Airbus A321neo
airliner, stretched series of the A320neo family
The Airbus A321neo is a narrow-body single-aisle airliner created by Airbus. The A321neo (neo being an acronym for "new engine option") was developed from the Airbus A321 and is part of the Airbus A320neo family, alongside the A319neo and A320neo, being the longest member of the family. It typically seats 180 to 220 passengers in a two-class configuration, with up to 244 passengers in a high-density arrangement.
The A321neo was announced by Airbus in December 2010, as an improvement and replacement to the A321ceo. Fitted with new engines and sharklets as standard, the A321neo has the longest fuselage of any Airbus narrow-body airliner in commercial use. Available with either CFM International LEAP-1A or Pratt & Whitney PW1100G-JM engines, Airbus advertises a 20% increase in fuel efficiency per passenger, with 500 nautical miles (930 km; 580 mi) more range, or 2 tonnes (4,400 lb) more of payload. Boeing introduced a new generation of their competing narrowbody family, the 737 MAX, nine days before the introduction of the A321neo.
The A321neo has the same overall length as the A321ceo, with an increased fuel efficiency and performance rating. The A321neo has a range of 3,995 nautical miles (7,399 km), with an MTOW (maximum take-off weight) of 97 tonnes (214,000 lb), and its engine has 109 to 156 kN (24,500 to 35,000 lb) of thrust.
The A321neo began production in 2016, with final assembly taking place in Hamburg, Germany, as well as in Toulouse, France; Mobile, United States, and Tianjin, China.
“Airbus A321neo” enters the record as airliner, stretched series of the A320neo family. Crown Archives preserves that source wording while asking what Airbus, A321neo and airliner can confirm, complicate or overturn.
Why this record matters
“Airbus A321neo” is worth following because a concise public description often conceals a longer documentary argument. Here, Airbus, A321neo and airliner provides the most credible route into that argument.
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 18, 2026. The linked authority identifier is Q30914140. None of the 0 selected statements returned an explicit reference. The first chronological checks are 2010 and 2016.
Overview language is designed for orientation and should not be treated as a substitute for the evidence cited beneath it. The lead is largely declarative, so disagreement and counter-evidence require a deliberate search beyond the opening account. 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 “Airbus A321neo”, its source revision and the description used here.
- Expand the search: follow Airbus A321neo primary sources, Airbus A321neo archive and Airbus 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 “Airbus A321neo”?
- Which institution is responsible for the underlying evidence?
- What terminology or title could unlock a more precise catalogue search?
Search terms from this dossier
This entry incorporates text from “Airbus A321neo” 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.