Austin FX4
motor vehicle

The Austin FX4 is a hackney carriage that was produced from 1958 until 1997. It was sold by Austin from 1958 until 1982, when Carbodies, who had been producing the FX4 for Austin, took over the intellectual rights to the car. Carbodies only produced the FX4 for two years, until 1984, when London Taxis International took over rights and continued producing it until 1997. In all, more than 75,000 FX4s were built. Over its lifetime, the FX4 increasingly became regarded as a design classic, and a visual icon of London recognised throughout the world, to the point where its eventual successors - the TX-series and the current LEVC TX - continue the FX4's basic styling cues and overall aesthetic.
Design and launch
The FX4 London taxi was the successor to the Austin FX3, produced between 1948 and 1958, and in its day, the FX4 the most widely used taxi in London. Like the FX3, the FX4 was designed by Austin in collaboration with Mann & Overton, the London taxi dealership that commissioned it (and paid for half of its cost) and Carbodies, the coachbuilder that built the body and assembled the cab ready for sale. The design team included Albert Moore from Austin's engineering division, Jack Hellberg from Carbodies and David Southwell of Mann & Overton. The original design was by Austin's Eric Bailey and it was engineered for production by Carbodies' Jake Donaldson. It would be the first London taxi to go into production that had four doors, since earlier London taxis had featured a luggage platform that was open to the elements on the pavement/sidewalk side in lieu of a front passenger seat.
Begin with the source’s own compact description: “Austin FX4” is motor vehicle. The dossier treats that line as a proposition to test through Austin, motor and vehicle, not as a finished interpretation.
Why this record matters
The phrase “motor vehicle” 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.
Named sources, stable identifiers and responsible institutions provide the strongest route from overview to verifiable evidence. The source revision retrieved here is dated Aug 1, 2026. The linked authority identifier is Q781084. None of the 0 selected statements returned an explicit reference. The first chronological checks are 1958, 1997, 1982 and 1984.
A concise general-reference account can conceal disagreements about scope, terminology or the weight assigned to individual sources. 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 “Austin FX4”, its source revision and the description used here.
- Expand the search: follow Austin FX4 primary sources, Austin FX4 archive and Austin 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 “Austin FX4”?
- What terminology or title could unlock a more precise catalogue search?
- Which cited source is closest to the event, object or claim?
Search terms from this dossier
This entry incorporates text from “Austin FX4” 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.