NYC99LA158 · Boeing Stearman E75
Boeing Stearman E75 · Accident: nose over during landing
From Cape Cod Airport (2B1) to an unrecorded destination
Event
- NTSB case
- NYC99LA158
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 0 · all aircraft and ground
- Ground fatalities
- 0
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Boeing Stearman E75
- Aircraft type
- Boeing Stearman E75
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N1658M
- Operator
- Richard A. Kornhiser · private individual
- Onboard fatalities
- Unknown
- Route
- From Cape Cod Airport (2B1)To not recorded
- Aircraft age
- Not recorded
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 91: General Aviation
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- Landing · landing roll
- First occurrenceThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Nose over
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Passenger › Control interference, inadvertent
Not plotted · Location withheld: coordinates are missing, conflicting, invalid, or have no accepted acquisition method. No substitute location has been invented.
NTSB narrative
The pilot, who was in the rear seat of the airplane, stated that after touching down on Runway 27, a 2,680 foot-long grass runway, the airplane suddenly nosed over, and came to rest inverted. After the accident, the pilot asked his pilot rated passenger, who was seated in the forward seat, if he had his feet on the brakes. The passenger replied yes. The pilot additionally stated that he did not brief the passenger on the operation or use of the brakes prior to flight, and there were no means of communication while the airplane was in flight.
Probable cause
The inadvertent control interference of the airplane's brakes by the passenger. A factor related to the accident was the pilot in commands insufficient passenger briefing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC99LA158
- Event ID
- 20001212X19333
- Case number
- NYC99LA158
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: investigation status. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: 842a72d7db2dcdf30f27ecb9b3cddde4540d2c053e231d1c4e3a7fe5718c175b; retrieved 2026-09-22T14:38:15.271Z.