"What we’re doing right now is we’re building our system today, and we’re getting ready for the future," John Sneden said at the Life Cycle Industry Days conference in Dayton — a comment that frames a growing timing problem for two linked Air Force programs.
John Sneden and the NGAP timeline
At Dayton, John Sneden, the Portfolio Acquisition Executive in charge of the Propulsion Directorate at the Air Force Life Cycle Management Center (AFLCMC), said the Air Force is "getting ready for potential [NGAP] integration activities in the 2030 timeframe," according to reporting by Breaking Defense. That statement sits alongside budget language and program milestones: NGAP’s "Prototype Fabrication & Engine Assessment" phase is planned to run through at least September 2031, and the service’s budget request shows a projected spending surge — nearly $513.7 million in the upcoming fiscal cycle, followed by $905.7 million in Fiscal Year 2028 and $865 million in Fiscal Year 2029, then dropping to roughly $300 million annually in FY2030–2031.
Sneden told Air & Space Forces Magazine that "what is reflected in the budget outlay is really about building engines, testing engines, and then we’ll be rolling through that competitively over the next few years," and that "initial hardware is procured, their design meets our standards, everything is clean from that end, and both vendors have been able to do that."
XA102 and XA103 — General Electric and Pratt & Whitney (RTX)
The two competing NGAP vendors named in Air Force disclosures are General Electric and Pratt & Whitney (a subsidiary of Raytheon, now called RTX). Both firms completed assembly readiness reviews for their respective designs, the XA102 and XA103, in May. The Air Force raised the cost ceilings on those contracts to $3.5 billion last year; the deals cover work through 2032.
Both designs are adaptive-cycle engines — broadly described in the reporting as engines that can operate like a turbofan for economy and like a turbojet for power — and both have drawn on work from the earlier Adaptive Engine Transition Program (AETP). AETP was cancelled in 2023; the Air Force has shifted to upgrades for the existing Pratt & Whitney F135 instead of continuing AETP for the F-35.
Public comparisons cited by the reporting show past claims that General Electric’s XA100 (the AETP design) was about 25 percent more efficient than the F135 and offered 10–20 percent more thrust in certain profiles. The NGAP vendors continue to pursue competitive prototypes and testing, including engine hardware and rigs such as the three-stream fan tests reported at Arnold Engineering Development Complex.
F-47 flight schedule and the propulsion mismatch
The F-47 is targeted to make its maiden flight in 2028, while Sneden indicated the Air Force does not expect an NGAP engine to be ready for integration until 2030. That timing disconnect raises the practical likelihood that the first F-47 prototypes — and possibly initial production batches if schedules hold — will fly with engines other than the NGAP designs.
The reporting notes precedent for this approach: early XF-104 prototypes flew with Wright J65 turbojets while waiting for the intended General Electric J79; early F-14As used Pratt & Whitney TF30s until General Electric F110s were later integrated. The article also references similar spiral developments in China’s J-20 and Russia’s Su-57 programs.
Available in-production engines cited as plausible interim options include the Pratt & Whitney F135 and F100, and the General Electric F110. The F119—found on the F-22 and described in the reporting as "out of production, at least as far as we know"—is mentioned as another potential stopgap for flight testing. The F-47’s design goals — specifically the expectation to supercruise and operate at very high altitudes — mean that an F119-like capability is singled out in the reporting as relevant to the jet’s performance envelope.
Airframe constraints, intakes, and retrofit costs
The story highlights practical integration constraints that complicate swapping engines mid-program. Physical trade space for engines, fuel systems, cooling and accessory power are described as largely static; intake geometry is critical for reliable operation and is especially complicated on stealthy designs. The article notes the high cost and complexity of integrating advanced engines can make later refits infeasible, citing the AETP experience and its cancellation as an example of how propulsion-engine integration challenges can drive program decisions.
Sneden encapsulated the program posture when he told Air & Space Forces Magazine: "We built NGAP as essentially an agnostic system... build the system first, open up options for the future," and added, "Not everything has to have an adaptive fan," underscoring an intent to preserve flexibility across platforms.
What this means for General Electric and Pratt & Whitney, the U.S. Air Force, and Boeing
- General Electric and Pratt & Whitney (RTX): Both companies will continue prototype assembly, testing, and competitive qualification as NGAP funding ramps in FY2028–FY2029 and hardware is built for assessment through 2031–2032.
- The U.S. Air Force / AFLCMC: Program managers must reconcile NGAP’s 2030 integration readiness with the F-47’s 2028 first flight target, balance budget surges, and decide whether to accept interim propulsion for early flights and initial fielding in the early 2030s.
- Boeing: The airframe builder faces schedule pressure to meet 2028 flight-test milestones and to accommodate either an interim engine or later NGAP integration, a choice that will affect early performance and potential structural or inlet redesign requirements.
If the schedules hold, the factual record shows the F-47 will face an early propulsion choice: begin flight and initial fielding with an existing engine or delay to wait for NGAP integration in 2030. The Air Force’s next concrete milestones to watch are the F-47’s planned 2028 first flight and NGAP’s readiness for integration around 2030 — decisions at that intersection will determine whether early F-47s fly with interim engines and how close those early examples come to the platform’s intended range and performance.
