FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CHI00LA216 · Monocoupe 90A

25 Jul 2000 · Creve Coeur, MO, United States

Monocoupe 90A · Accident: nose over during landing

From 1H0 to an unrecorded destination

Report a problem

Event

NTSB case
CHI00LA216
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

Monocoupe 90A

Aircraft type
Monocoupe 90
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
N19429
Operator
Unknown
Onboard fatalities
Unknown
Route
From 1H0To 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

  • Copilot/second pilot › Brakes(normal), excessive

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The flight was conducted to allow the owner to accrue two hours of instruction for insurance purposes. The flight instructor was performing a landing when the accident occurred. According to a statement by the owner, "During landing roll-out aircraft drifted toward right side of runway at which time the instructor exclaimed 'I don't have brakes over here'. Brakes were applied by trainee [owner] causing aircraft to nose over and come to rest on its back." Brakes were installed only in the left seat position. The flight instructor was seated in the right seat position. No pre-existing anomalies were found during a postaccident inspection of the aircraft.

Probable cause

the excessive brakes applied by the second pilot. A factor to the accident was the unavailability of brakes on the flight instructor's side of the aircraft.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CHI00LA216
Event ID
20001212X21405
Case number
CHI00LA216
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: 92f817b74f4d79f70bda3fb5921dafc361e2e5c463cc1e494f26c4659c8b737f; retrieved 2026-09-22T12:39:23.731Z.