1964 Lotus Type 34 Indianapolis Car
Explore the 1964 Lotus Type 34 Indianapolis Car: programme history, design, verified rarity scope, specifications and credited photography.

The 1964 Lotus Type 34 develops the Indianapolis project after the Type 29. Its separate register and oval-racing role preserve an important stage before Lotus’s later Indianapolis victory.
History and verified programme identity
Classic Team Lotus identifies the Type 34 as a development of the Type 29 informed by the team’s 1963 Indianapolis experience. The custodial record states that Ford engines were used and lists three entries. That defines a small competition Type, with the register reference retained independently of any present survivor estimate. The programme is not the later Type 38 and is not illustrated with a Type 38 photograph. The supplied image is explicitly creator-identified as a 1964 Type 34.
Engineering and design
An Indianapolis development has to respond to the experience of running an earlier car on the oval. The body, fuel provision and running gear belong to a purpose different from a compact road-circuit Formula car. The Type 34’s front-quarter museum view makes its long central body and open wheels clear. The custodian’s account supplies the design relationship; the photograph does not by itself reveal every alteration from the Type 29. Detailed tyre, suspension and engine claims need the record of the relevant chassis and race configuration, especially where later restoration has changed the visible presentation.
The physical car in the supplied photograph
The supplied photograph shows a green-and-yellow Type 34 in an indoor collection in June 2022, photographed by Sarah Stierch under the creator name Missvain. Its narrow cockpit, exposed wheels and long yellow nose are visible. The source title identifies the 1964 model, while the image date records the later exhibition appearance.
A closer look at the programme
The museum setting lets the viewer study the long body at rest. A bright nose and dark green upper surface organize the silhouette, but colour cannot establish an original entrant. The useful connection is between the identified exhibit and the primary Type record. Individual history then determines which event configuration it represents. This avoids using a famous later Lotus victory as a shortcut to interpret an earlier car, while still making the Indianapolis development sequence accessible to a reader encountering the models for the first time. The indoor Type 34 photograph shows the front wheel spacing and long nose in the same frame. Its yellow front surface contrasts with the dark cockpit surround, making the small occupied area obvious within the larger racing body. The museum context supplies a later place to study the car, rather than an original event claim. This is a useful way to introduce the Indianapolis design problem: the visible object has its own proportions, while the primary record explains its relationship with the earlier Type 29. Together they give the programme an identity beyond a familiar team colour scheme.
Collecting and chassis evidence
The three register entries are a starting point for individual provenance, not proof that every present Type 34-shaped car has an unchanged original chassis. Delivery records, race entries and dated repairs would connect a specific exhibit to its original identity. Keep the individual photo separate from claims about another entrant’s qualifying result. A model can be historically important without giving every illustrated chassis the same driver or finishing position.
Related Lotus designs and meaningful comparisons
The Type 38 is the later Indianapolis comparison, while the Type 56 demonstrates how radically Lotus’s oval-racing approach could change. The Type 34 belongs to the earlier Ford-powered sequence, and those later achievements do not replace its own record. Separate programme profiles preserve both continuity and the different engineering questions explored at each stage.
Reading the sources
The programme sources and the photograph answer different questions. Manufacturer and custodial records establish the original model, Type, category and published production scope. The creator’s file establishes the pictured subject, setting and image permission. An individual chassis history can then add ownership, competition entries and dated repairs without changing the scope of the original programme. Build references are not survivor counts, and a later specification does not automatically become an additional newly manufactured vehicle. Where primary evidence does not establish a complete fabrication census, that field remains unassigned.
Specifications and rarity evidence
| Programme reference year | 1964 |
|---|---|
| Model / Type | Type 34 Indianapolis Car — Type 34 |
| Body / competition role | Ford-powered Indianapolis development |
| Programme year | 1964 |
| Design relationship | Development of Type 29 |
| Powertrain reference | Ford engine programme |
| Register scope | Three listed entries |
| Photo date | June 2022 |
| Published build / register reference | 3 listed register entries |
| Independently audited completed tally | Not assigned |
| Count scope | Published source reference: 3 listed register entries. Scope follows the named programme or register; independently audited completed output and survivor census remain unassigned. |
| Original inventory status | LOT-033 — Verified |
Frequently asked questions
Is this the 1965 Indianapolis-winning Type 38?
No. The Type 34 is a separate 1964 programme and the supplied photo identifies that model. The Type 38 has its own profile.
How is Type 34 Indianapolis Car classified?
This is a Team Lotus competition Type archive. It remains separate from Lotus road-car production. Customer cars, works entries and converted chassis need a reconciled scope before any complete fabrication tally is assigned.
Which technical details are established for the programme?
The primary record supports programme year: 1964; design relationship: Development of Type 29; powertrain reference: Ford engine programme. These are programme or explicitly attributed photo references. A particular surviving car’s engine, chassis repairs and competition preparation require its own dated documentation.
Does the photographed appearance establish factory originality?
The caption records a real creator-identified Type 34 Indianapolis Car subject and its later setting. It establishes the illustration’s scope, while original components, restoration work and individual race provenance require chassis-specific evidence. A competition number, current paint or museum display is not used as an originality certificate.
What rarity or archive scope is verified?
Published source reference: 3 listed register entries. Scope follows the named programme or register; independently audited completed output and survivor census remain unassigned.
Who photographed the supplied image?
Missvain via Wikimedia Commons, under CC BY 4.0. The original file and licence are linked with the image. Retain the creator, source and licence when uploading, exporting or reusing it; local retouching and synthetic enlargement have not been performed.
Related Lotus profiles
Sources and photo credits
Photograph: Missvain via Wikimedia Commons original source, CC BY 4.0. Source-provided thumbnail supplied without local cropping, retouching or synthetic enlargement.
Built in limited numbers
Published source reference: 3 listed register entries. Scope follows the named programme or register; independently audited completed output and survivor census remain unassigned.
Gallery
Specifications
Factory specifications may vary by model year, market and configuration.
Identity & production
- Official model
- Type 34 Indianapolis Car


