The U.S. aircraft register, updated daily
Accidents · NTSB CHI06FA154 · Final report

Piper PA-32R-301T accident near Parkville, Missouri, June 13, 2006

On June 13, 2006, a Piper PA-32R-301T, registered N292HH, was destroyed in an accident near Parkville, Missouri (Kansas City International airport). It was a personal flight under general aviation rules (Part 91). 2 people were killed. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The pilot's improperly planned approach which resulted in the encounter with wake turbulence while the airplane's airspeed exceeded maneuvering speed. This encounter resulted in the subsequent loss of aircraft control and the in-flight separation of the left and right sides of the stabilator and the left wing.

Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.

What the record shows

Date
June 13, 2006
Place
Parkville, Missouri · Kansas City International · map
Type
Accident
Injuries
2 people were killed.
Weather
visual conditions (good weather)
Aircraft
Piper PA-32R-301T · all PA-32R-301Ts on the register
Registration
N292HH · no longer on the register · serial 3257114
Damage
Destroyed
Flight
Personal flight · general aviation rules (Part 91)

The NTSB's narrative final · quoted from the NTSB record

The airplane experienced an in-flight break-up during a visual approach to runway 01L. Radar data indicated the airplane crossed the flight path twice of a Boeing 737 that was landing on parallel runway 01R. The first time N292HH crossed the path of the Boeing 737 was about 1910:48 at an altitude of about 3,900 feet msl at an airspeed of 158 KCAS. The Boeing 737 had been at the same geographic point approximately 2-minutes and 9-seconds prior, at an altitude of about 5,500 feet msl. The second time N292HH crossed the flight path of the Boeing 737 was about 1911:25 at an altitude of about 3,300 feet msl at an airspeed of 183 KCAS. The Boeing 737 had been at the same geographic point approximately 1-minute 55-seconds prior at an altitude of 3,900 feet msl. The Boeing was on a north-northwesterly heading at the time and N292HH was on a northwesterly heading. After crossing the flight path N292HH continued to the west of the Boeing 737's path. The last radar contact with N292HH was at a point 0.32 miles west of the flight path of the Boeing 737. The last radar contact was at 1911:34 at an altitude of 3,128 feet msl with an airspeed of 183 KCAS. All of the wreckage was located in one open field. The left wing, both the left and right sides of the stabilator, along with portions of the right wing flap and aileron separated in-flight. According to the Pilot's Operating Handbook the never exceed speed (Vne) for N292HH was listed as being 189 KCAS. The handbook showed the maximum structural cruising speed as 165 KCAS. The design maneuvering speed (Va) was listed as being 132 KCAS at 3,600 pounds and 104 KCAS at 2,230 pounds. The inboard sections of the left and right sides of the stabilator along with the separated section of the left wing spar were sent to the NTSB Material Laboratory for examination where it was determined that all of the separations were as a result of overload. FAA Advisory Circular (AC) 90-23F addresses Aircraft Wake Turbulence. AC 90-23F states, "Flight tests have shown that the vortices from larger (transport category) aircraft sink at a rate of several hundred feet per minute, slowing their descent and diminishing in strength with time and distance behind the generating aircraft. Pilots should fly at or above the preceding aircraft's flight path, altering course as necessary to avoid the area behind and below the generating aircraft." AC 90-23F also states, "WHETHER OR NOT A WARNING OR INFORMATION HAS BEEN GIVEN, HOWEVER, THE PILOT IS EXPECTED TO ADJUST AIRCRAFT OPERATIONS AND FLIGHT PATH AS NECESSARY TO PRECLUDE SERIOUS WAKE ENCOUNTERS." According to the hourly weather observations taken prior to and after the accident the winds were from the northeast between 9 and 10 knots.

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The factual record from the NTSB's investigation tables, in plain English

Pilot

  • Certificate: private
  • Ratings: single-engine land; instrument: airplane
  • Flight time: 579 hours in all; 43 in this make and model; 85 in the last 90 days; 17 in the last 30 days; 451 as pilot in command
  • Last flight review: April 1, 2006
  • Medical certificate: Class 3
  • Seat: left
  • Injury: fatal

The aircraft

  • Airframe total time: 1,272 hours
  • Last inspection: annual inspection, June 1, 2005
  • Seats: 6
  • Landing gear: retractable
  • Engine: Lycoming TIO-540-AH1A (piston); 0 hours total

The flight

  • Departed from: K15 Osage Beach MO
  • Destination: MCI Kansas City MO
  • Flight plan: IFR
  • A second pilot was aboard

Weather at the time

  • Light: daylight
  • Wind: from 050° at 8 knots
  • Visibility: 10 statute miles
  • Sky: broken clouds at 20,000 ft; scat at 3,000 ft
  • Temperature: 72°F (22°C), dew point 57°F (14°C)
  • Altimeter: 30.13 inHg
  • Observation at 11:53 pm from MCI, 6 miles away

Injuries

FatalSeriousMinorNone
Crew1
Passengers1

Documents from the investigation the NTSB's docket: the evidence folder behind the report

The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), has not been read from the NTSB for this case yet; the list appears here once it has. Open the docket at the NTSB.

Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.