SEA02LA080 · Aeronca 7-EC
Aeronca 7-EC · Accident: on ground/water collision with object during landing
From Lenhardt Airpark (7S9) to Flying M Airport (OR05)
Narrative check · The NTSB narrative appears to contradict this record's departure or destination and aircraft involved. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- SEA02LA080
- 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
- Unknown
- 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
Aeronca 7-EC Possible conflict
- Aircraft type
- Aeronca 7
- 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
- N4712E
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route Possible conflict
- From Lenhardt Airpark (7S9), Lenhardt Field, ORTo Flying M Airport (OR05), Flying M Ranch, OR
- 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
- On ground/water collision with object
- 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 › Directional control, not maintained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
While flying past the Flying M Airstrip en route to another airport, the pilot decided to land there. He circled the airport twice to check traffic and the winds, and then entered a left hand pattern. He rolled out on final with a slight tailwind, but was still able to touch down approximately where he intended. Almost immediately after touching down on the 2130 foot strip, the pilot started applying the brakes because the tree line at the far end appeared closer than he had expected. As he attempted to bring the aircraft to a stop, it drifted off the right side of the landing surface, and its wing impacted the propeller of a parked aircraft. The pilot later said that he believes that if he had continued a normal rollout and applied the brakes after the aircraft had a chance to slow, he would have had no problem stopping in the required distance.
Probable cause
The pilot's failure to maintain directional control while applying the brakes during the landing roll. Factors include a tailwind and trees at the far end of the airstrip.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record SEA02LA080
- Event ID
- 20020521X00713
- Case number
- SEA02LA080
- 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: 3144033eb30fa6801403e677445198615dea46399082fc214ec2d4e1cb21a0c9; retrieved 2026-09-22T10:56:25.820Z.