CEN24FA295 · Piper PA-28-180
Piper PA-28-180 · Accident: fire/smoke (post-impact)
From Sioux Falls Regional Airport (FSD) to Chan Gurney Municipal Airport (YKN)
Event
- NTSB case
- CEN24FA295
- 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
- 1 · 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 PA-28-180
- Aircraft type
- Piper PA-28
- 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
- N903US
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Sioux Falls Regional Airport (FSD), Sioux Falls, SDTo Chan Gurney Municipal Airport (YKN), Yankton, SD
- Aircraft age
- About 58 years (built 1966)
- 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
- Post-impact
- 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
- Fire/smoke (post-impact)
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Aircraft › Aircraft oper/perf/capability
- Environmental issues › Conditions/weather/phenomena
- Environmental issues › Physical environment
- Personnel issues › Action/decision
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
On July 31, 2024, about 0720 central daylight time, a Piper PA-28-180 airplane, N903US, was destroyed when it was involved in an accident near Irene, South Dakota. The pilot was fatally injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. The pilot held a private pilot certificate for single-engine airplanes and did not have an instrument rating. No flight plan had been filed and the pilot was not in contact with air traffic control. It was reported that the airplane was being flown from Joe Foss Field Airport (FSD), Sioux Falls, South Dakota, to Chan Gurney Municipal Airport (YKN), Yankton, South Dakota, to have maintenance performed. A review of the weather data around the time of the accident showed that conditions at the intended destination airport were 1/4 statute mile visibility and fog with ceilings broken at 200 ft and overcast at 1,900 ft. According to Automatic Dependent Surveillance-Broadcast (ADS-B) data, the airplane departed from Joe Foss Field Airport, Sioux Falls, South Dakota, at 0701. The airplane proceeded on a predominantly southwest heading at 3,700 ft mean sea level (msl). At 0718, a descent began and continued until the last recorded data point at 0720:52. During the final minute of recorded data, the airplane made a descending left turn to the south followed by a descending right turn when the data ended. The final data point was about 400 ft east of the airplane’s final resting point (Figure 1).
Figure 1. 3D representation of the final portion of the flight of N903US The airplane came to rest in an agricultural field on a south heading. A postimpact fire ensued and consumed the cockpit and most of the forward fuselage. The main wreckage was about 100 ft west of a north-south gravel road, and broken tree limbs were found to the east that bordered the road. All structural components and flight control surfaces were located along the wreckage debris path or amongst the main wreckage.
Figure 2. View of main wreckage at the accident site. The left wing remained intact and attached to the fuselage and had extensive fire damage to the inboard end. The left flap and aileron remained connected to their respective attach points on the wing. The right wing was separated from the fuselage and found next to it, with outboard end displaced rearward. About 4 ft of the outboard right wing, was separated and found on the opposite side of the road. The separated portion of wing had a semi-circular dent in the leading edge consistent with a tree strike. There were small pieces of tree limb fragments within the wing leading edge skin. The right flap remained attached to the larger inboard portion of the right wing. The aileron remained partially attached to the larger portion of the right wing. The flaps were found in the retracted position.
Figure 3. Outboard section of right wing with evidence of tree impact. The fuselage exhibited extensive fire damage with most of the cabin structure consumed by the postimpact fire. The firewall exhibited rearward crushing. The aft fuselage was partially intact with thermal damage. The empennage remained attached to the fuselage with all control surfaces. The vertical tail, rudder and left horizontal stabilator had no damage except that from the postimpact fire. The right side of the horizontal stabilator had extensive thermal damage and appeared to be bent downward at the leading edge. Post accident examination revealed that there were no anomalies found with the engine would have precluded normal operations. The propeller exhibited chordwise scaring, S-shape bending, and leading edge gouging, consistent with power production at the time of impact. Flight control continuity was established to the extent possible with the condition of the wreckage. All flight control cables remained attached from their respective control surfaces to the cockpit except for a single break in the aileron drive control cable. The break was about 3 inches from its attachment to the cable near the control column. The break was consistent with overload damage.
Verbatim NTSB factual narrative from the NTSB dataset
Sources
NTSB record CEN24FA295
- Event ID
- 20240731194815
- Case number
- CEN24FA295
- 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, cause areas. 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: 23309c895cb41eb9ff79635cc0a10cd9d12a0fea4e25e3eee6f89d8b9202ec0f; retrieved 2026-09-15T08:25:39.554Z.