GAA16LA128 · Piper PA24 250
Piper PA24 250 · Accident: controlled flight into terrain/object (CFIT) on approach
From Jamestown Regional Airport (JMS) to Sturgis Municipal Airport (49B)
Event
- NTSB case
- GAA16LA128
- 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
- Instrument Meteorological Cond
Piper PA24 250
- Aircraft type
- Piper PA24
- 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
- N6691P
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Jamestown Regional Airport (JMS), Jamestown, NDTo Sturgis Municipal Airport (49B), Sturgis, SD
- Aircraft age
- About 56 years (built 1960)
- 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 · IFR missed approach
- Defining eventThe 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
- Controlled flight into terrain/object (CFIT)
- 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
- 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
- Personnel issues › Action/decision
- Personnel issues › Task performance
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 he was conducting an instrument approach in instrument meteorological conditions. Upon reaching the decision altitude, the front seat passenger reported the runway was in front of the airplane. The pilot looked up from the instruments, but could not see the runway out the windscreen or the side window. Referring back to the flight instruments, the pilot noted that the airplane was level, but he was unable to determine the airplane's altitude and did not know where the airplane was in relation to the runway. The pilot then applied full engine power and began to climb the airplane; however, the airplane's right wing impacted a light pole. The airplane immediately pitched nose-down and descended into terrain. The pilot reported there were no mechanical malfunctions or anomalies with the airplane that would have precluded normal operation, and that the accident could have been prevented if he had immediately executed a missed approach at the decision altitude.
Probable cause
The pilot's failure to execute the published missed approach procedure in a timely manner, which resulted in collision with a light pole and subsequent impact with terrain.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record GAA16LA128
- Event ID
- 20160216X33929
- Case number
- GAA16LA128
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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: 7384dbe3639221e0eca11605e609dc845af52b7801022af09f6363418289cba6; retrieved 2026-09-16T03:09:44.979Z.