SEA92LA208 · Luscombe 8A
Luscombe 8A · Accident: nose over during landing
From 3S2 · Aurora, OR to an unrecorded destination
Event
- NTSB case
- SEA92LA208
- 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
Luscombe 8A
- Aircraft type
- Luscombe 8
- 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
- N39039
- Operator
- Wirt, Daniel P. · private individual
- Onboard fatalities
- Unknown
- Route
- From 3S2 · Aurora, ORTo 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
- Pilot in command › Brakes(normal), excessive
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
UPON ARRIVAL AT THE AIRPORT THE PILOT IN COMMAND PERCEIVED AN UPHILL GRADIENT AS WELL AS A 5-10 KNOT WIND OUT OF THE WEST. CHOOSING TO LAND TO THE EAST DUE TO THE GRADIENT HE TOUCHED DOWN WITHIN THE FIRST 25% OF THE RUNWAY. THE PILOT REPORTED THAT DURING THE ROLLOUT HE 'APPLIED BRAKES, (BUT THE) AIRCRAFT WAS GOING TOO FAST AND FLIPPED OVER.'
Probable cause
THE EXCESSIVE APPLICATION OF THE BRAKES BY THE PILOT IN COMMAND. FACTORS CONTRIBUTING TO THE ACCIDENT WERE THE TAILWIND AND THE PILOTS VISUAL (MIS)PERCEPTION OF RUNWAY GRADIENT.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record SEA92LA208
- Event ID
- 20001211X15780
- Case number
- SEA92LA208
- 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: 1fb377043a9f58e811be30ab3a5ef942208136dfdcc5e46caad71d1204291b0c; retrieved 2026-09-23T02:36:53.101Z.