Safewing Aviation Piper PA-23-250 accident
Piper PA-23-250 · Accident: in flight encounter with weather en route
From Charles B. Wheeler Downtown Airport (MKC) to Wichita Dwight D. Eisenhower National Airport (ICT)
Event
- NTSB case
- DEN06LA050
- 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
- Charter & commuter
- 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-23-250
- Aircraft type
- Piper PA-23
- 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
- N331FC
- Operator
- Safewing Aviation
- Onboard fatalities
- Unknown
- Route
- From Charles B. Wheeler Downtown Airport (MKC), Kansas City, MOTo Wichita Dwight D. Eisenhower National Airport (ICT), Wichita, KS
- 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 135: Air Taxi & Commuter
- 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
- En route · cruise
- 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 encounter with weather
- 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
- Tree(s)
- 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 possible
- Pilot in command › Flight into adverse weather, attempted
- Pilot in command › In-flight planning/decision, improper
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
Prior to departure, the pilot obtained a weather briefing from a flight service station. At the start of the briefing conversation, the briefer asked the pilot if he was going to take the "anti-icing" equipped airplane for the proposed flight. The pilot responded, "Hopefully." The briefer informed the pilot "there's all kinds of stuff going on out there today, looks like you're going to need [anti-icing equipped airplane]. The briefer told the pilot to expect ice, instrument flight rules (IFR) conditions, and turbulence along the intended route of flight. The briefer informed the pilot the weather consisted of rime ice, mix clouds, and precipitation, which included mist, snow, sleet, and rain. The briefer stated the current freezing level at the departure airport was 1,500 feet agl, to which the pilot stated, "Alright." The briefer inquired whether the pilot had an alternate airport, the pilot responded, "no." According to air traffic control communications, shortly after takeoff, the airplane climbed to 4,000 feet and the controller identified the airplane on radar. The pilot informed the controller the airplane was accumulating "very little ice", and he requested an altitude of 6,000 feet. The controller cleared the pilot to 6,000 feet, and shortly thereafter, the pilot requested an altitude of 3,000, because the airplane would not climb. The controller cleared the airplane to 3,200 feet, which was the minimum en route altitude for the area. The pilot then requested to divert to a nearby airport. The pilot requested the weather for the airport and stated he could hardly keep altitude because the airplane "had a lot of ice." The controller reported to the pilot that radar contact was lost below 3,200 feet, at which the pilot responded, "can't find the approach plates for [airport], hardly hold altitude at 3,200 feet, losing altitude." The controller then asked, "Are you picking up ice?" The pilot responded, "Lot of ice." The pilot inquired whether he could descend and the controller cleared the pilot to descend at his discretion. The controller asked the pilot if he could navigate an approach to the airport, and the pilot responded, "No sir, I'm going down." During an attempted forced landing, the airplane impacted a tree, and came to rest upright in a field approximately 4 miles southeast of the airport. In an interview after the accident, the pilot reported no anomalies with the airplane's deice equipment. The pilot stated it was somewhat difficult to see the extent of the ice accumulation because the flight occurred prior to sunrise. Examination of the airplane revealed no anomalies with the airframe, systems and engines.
Probable cause
the pilot's attempted flight into adverse weather conditions and improper in-flight planning which resulted in loss of control and subsequent impact with trees. Contributing factors were the pilot's delayed remedial action, the icing and dark night conditions.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DEN06LA050
- Event ID
- 20060323X00332
- Case number
- DEN06LA050
- 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: 65136bbcd35914c84857a79ad3a018b60010d19985c0c5760d4513950966bb0a; retrieved 2026-09-18T14:54:38.765Z.