General Electric GEnx
turbofan jet engine
The General Electric GEnx ("General Electric Next-generation") is an advanced dual rotor, axial flow, high-bypass turbofan jet engine in production by GE Aerospace. It is one of two engine options available for the Boeing 787 Dreamliner, and it was also produced for the Boeing 747-8. The GEnx succeeds the CF6 in GE's product line.
Development
In 2004 the GEnx and the Rolls-Royce Trent 1000 were selected by Boeing after evaluating proposals from GE, RR and P&W, with the PW-EXX. The GEnx uses some technology from the GE90 turbofan, including swept composite fan blades and the 10-stage high-pressure compressor (HPC) featured in earlier variants of the engine. It also uses composite materials in the fan case.
The engine market for the 787 is estimated at US$40 billion over the next 25 years. GE eliminated the bleed air system using high temperature/high pressure air from the propulsion engines to power aircraft systems such as the starting, air-conditioning and anti-ice systems. Both engines enable the move towards the More Electric Aircraft, that is, the concept of replacing previously hydraulic and pneumatic systems with electrical ones to reduce weight, increase efficiency, and reduce maintenance requirements.
The GEnx was expected to produce thrust from 53,000 to 75,000 lbf (240 to 330 kN) with first tests commencing in 2006 and service entry by 2008 (delayed by 787 deliveries). Boeing predicted reduced fuel consumption of up to 20% and significantly lower noise than previous turbofan engines.
Begin with the source’s own compact description: “General Electric GEnx” is turbofan jet engine. The dossier treats that line as a proposition to test through General, Electric and GEnx, not as a finished interpretation.
Why this record matters
The phrase “turbofan jet engine” supplies a clear boundary for inquiry. It also exposes the unanswered questions: who defined that boundary, when it became stable and which sources sit outside it.
Vocabulary and entity names are the principal evidence signals here, because they determine the precision of every later search. The source revision retrieved here is dated Sep 17, 2026. The linked authority identifier is Q1501584. 1 of 1 selected statements include explicit references; 1 carry qualifiers and 0 use preferred rank. The first chronological checks are 2004, 1000, 2006 and 2008.
Overview language is designed for orientation and should not be treated as a substitute for the evidence cited beneath it. The source lead contains qualifying language; that uncertainty should survive quotation, summary and reuse. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.
How to read it
Use the entry as an orientation point, then follow its citations and revision history. Names, dates and institutional relationships should be checked against the original record.
- Subject orientation
- Search vocabulary
- Locating named sources
The closest primary source, responsible institution and strongest cited specialist reference.
Three-step research path
- Establish the record: confirm the title “General Electric GEnx”, its source revision and the description used here.
- Expand the search: follow General Electric GEnx primary sources, General Electric GEnx archive and General research across catalogues and specialist indexes.
- Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.
Questions for further research
- Which source most directly establishes the central claim about “General Electric GEnx”?
- Which institution is responsible for the underlying evidence?
- Which cited source is closest to the event, object or claim?
Search terms from this dossier
This entry incorporates text from “General Electric GEnx” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.