SEA03LA199 · Wood Avid Magnum
Wood Avid Magnum · Accident: in flight collision with object during initial climb
From S80 · Grangeville, ID to Kooskia, ID
Event
- NTSB case
- SEA03LA199
- 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
Wood Avid Magnum
- Aircraft type
- Wood AVID MAGNUM
- 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
- N1214W
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From S80 · Grangeville, IDTo Kooskia, ID
- 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
- Initial climb
- 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
- Utility pole
- 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
No findings designated as a cause are recorded in the NTSB data yet.
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot reported that the first two attempts to land on the steep gravel surfaced airstrip resulted in bounced landings and a go-around. The third attempt resulted in another bounced landing that put the aircraft off the airstrip. Full power was applied and the pilot tried a severe banking maneuver to avoid a collision with a telephone pole. The left wing contacted the pole and its guy wire. The aircraft spun around and came to rest inverted in a field approximately 30 feet to the left of the airstrip and 30 feet distant from the east end. The pilot reported no mechanical failures or malfunctions with the aircraft at the time of the accident.
Probable cause
The pilot's improper recovery from a bounced landing which led to a loss of control.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record SEA03LA199
- Event ID
- 20031001X01645
- Case number
- SEA03LA199
- 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, coordinates. 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: c12fb9b3440e5213f1d474f1355d862e4e761f50246dd507a18f9f09dcf8978d; retrieved 2026-09-21T09:22:33.336Z.