SEA00LA137 · Beaver FERGUSON F-II FERGUSON F
Beaver FERGUSON F-II FERGUSON F · Accident: in flight collision with object on approach
From UNKNOWN to an unrecorded destination
Event
- NTSB case
- SEA00LA137
- 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
Beaver FERGUSON F-II FERGUSON F
- Aircraft type
- Beaver FERGUSON F-II
- 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
- N8228R
- Operator
- Gary D. Brons · private individual
- Onboard fatalities
- Unknown
- Route
- From UNKNOWNTo 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
- Approach
- 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
- In flight collision with object
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Stall/mush; Wire, transmission
- 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 › Airspeed, inadequate
- Pilot in command › Altitude/clearance, not maintained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot was approaching runway 01 at his strip from the southwest, with wind from the east-northeast at 10 to 15 knots. The pilot stated that on his approach to the runway, he had to cross over a north-south power line that was about 30 feet high. The pilot stated that just as the plane passed a row of 70-foot-high trees located to the right of the approach path, at an altitude of about 50 feet, he 'felt the plane stall.' The pilot stated he applied full throttle, but that the airplane 'did [not] respond quick enough to avoid the power line.' The pilot stated that the aircraft's left wheel caught and broke the power line, which 'threw the plane in a left downward [attitude with] the left wing hitting first then the nose.' The pilot reported: 'I had landed on this runway numerous times but never with this wind velocity or direction.' The pilot indicated that no mechanical malfunction or failure was involved in the accident, and that he felt the accident could have been prevented by 'faster [approach] speed [and] higher altitude.'
Probable cause
The pilot's failure to approach the strip with adequate airspeed for the conditions (resulting in a stall/mush situation), and his failure to maintain adequate altitude and/or clearance above a power line on the approach path. Factors included crosswind conditions, terrain-induced turbulence, and the power line.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record SEA00LA137
- Event ID
- 20001212X21612
- Case number
- SEA00LA137
- 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: 7e25f3e0fcefeefe5ab4779f545060e25ead935c6702c8f871b0588f22d05519; retrieved 2026-09-22T12:40:11.855Z.