FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Safewing Aviation Piper PA-32RT-300 accident

30 Jun 2005 · Kansas City, MO, United States

Piper PA-32RT-300 · Accident: in flight collision with object during takeoff

From Charles B. Wheeler Downtown Airport (MKC) to Wichita Dwight D. Eisenhower National Airport (ICT)

Report a problem

Event

NTSB case
CHI05LA160
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
Visual Meteorological Cond

Piper PA-32RT-300

Aircraft type
Piper PA-32
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
N21835
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
Takeoff
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
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

  • Pilot in command › Airspeed, 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

The airplane, on a non-scheduled domestic cargo flight, was destroyed on impact with a fence and levee on takeoff from runway 21. The pilot stated, "About 10 seconds after liftoff, aircraft started to descend. Impacted levee at end of runway, skidded over and came to rest on other side." The pilot reported that there were no mechanical malfunctions with the airplane. The air traffic controller on duty said that the winds were 310 degrees at 06 knots and further stated, "I observed [aircraft] backtaxi to [taxiway] Golf intersection of runway 21, turn around, and start departure roll. [Aircraft] was observed rotating abeam the highspeed taxiway." The pilot had private pilot privileges for single-engine land airplanes. The pilot took and passed an FAA Airman Competency/Proficiency Check in the same make and model single-engine airplane about two months prior to the accident. The pilot was found satisfactory in the examined flight maneuvers during that check ride. The airplane accumulated 0.1 hour since the 100-hour inspection. The pilot reported the weight of the cargo to be about 350 pounds and his calculated takeoff weight to be about 2,974 pounds. The cargo was removed from the wreckage and the cargo weighed 608 pounds. The post-accident calculated weight for the flight was 3,575 pounds. The airplane had a maximum gross weight of 3,600 pounds. The calculated takeoff ground roll distance for the flight was 2,200 feet and the calculated takeoff distance over a 50 foot obstacle was 4,000 feet. The runway distance available at intersection Golf on runway 21 was about 4,350 feet. Railroad, levee, and displaced thresholds are listed in the remarks for runway 3/21. Using the air traffic controller's reported winds, the calculated tailwind on runway 21 was one knot. The calculated headwind for runway 3 was one knot. Examination of the wreckage did not reveal any pre-impact anomalies.

Probable cause

The pilot not maintaining climb airspeed leading to the airplane's impact with the fence and terrain during takeoff. Factors in the accident were the pilot's inaccurate preflight planning calculations, the fence, and the levee.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CHI05LA160
Event ID
20051026X01734
Case number
CHI05LA160
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: bf681f3573439491ff8891e7e129e2d8e2b9fc3d500d7032e8271082ab9e2357; retrieved 2026-09-18T15:00:44.268Z.