SEA05FA037 · Aero Commander AC200D (Meyers)
Aero Commander AC200D (Meyers) · Accident: in flight collision with terrain/water while maneuvering
From Provo Municipal Airport (PVU) to Provo Municipal Airport (PVU)
Event
- NTSB case
- SEA05FA037
- 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
- 2 · 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
Aero Commander AC200D (Meyers)
- Aircraft type
- Aero Commander AC200
- 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
- N49J
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Provo Municipal Airport (PVU), Provo, UTTo Provo Municipal Airport (PVU), Provo, UT
- 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
- Maneuvering
- 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 terrain/water
- 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 › Aircraft control, not maintained
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
Data tracking extracted from the GPS found in the wreckage indicated that the aircraft accomplished several maneuvers of "race track" like turns to "360 degree" turns over the pilot's property at varying altitudes to below 500 feet above ground level and low airspeeds. The surviving passenger stated that the pilot and the front seat passenger were engaged in conversation discussing the property that they were maneuvering over, and felt that the pilot was distracted by the conversation, which was his first priority, and second was commanding the aircraft. On site documentation of the wreckage indicated that the aircraft collided with the flat open terrain in a nose down and left wing low attitude with the landing gear extended and the flaps extended to about 30 degrees. Post accident inspection of the airframe and engine did not reveal evidence of a mechanical failure or malfunction.
Probable cause
The pilot's failure to maintain aircraft control while maneuvering. Inadequate airspeed, the pilot's diverted attention, and low altitude flight were factors.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record SEA05FA037
- Event ID
- 20050124X00097
- Case number
- SEA05FA037
- 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: 9a051cc40998c2d81897bbd488212f81be692beee1a15b828a359a2bf83dbe1c; retrieved 2026-09-20T18:08:30.120Z.