1 fatality

2002-07-18: Piper PA-60 Aerostar (Ted Smith 600) (N158GA) — Grand Aire Express - Executive Aire Express — Columbus-Municipal (Bakalar), United States of America

Columbus-Municipal (Bakalar), United States of AmericaLanding (descent or approach)

On July 18, 2002, a Piper PA-60 Aerostar (Ted Smith 600) (registration N158GA) operated by Grand Aire Express - Executive Aire Express was involved in an aviation accident near Columbus-Municipal (Bakalar), United States of America during landing or approach. One person was killed. Investigators recorded the probable cause as: The pilot's failure to maintain control of the airplane during a missed approach. Additional factors included the operator's inadequate oversight, the pilot's improper in-flight decision, conditions conducive to pilot fatigue, fog, and night. This summary draws on records from the Bureau of Aircraft Accidents Archives (B3A); 3 related events involving the same aircraft type or operator are linked below.

Sourcesthe Bureau of Aircraft Accidents Archives (B3A)Primary reportUpdated 1781201737Data APIEditorial standards

An aircraft was destroyed after impacting the intersection of runways 23 and 32 during a missed approach. The pilot exceeded duty limits due to a freight delay. Thick fog was reported, and no preexisting anomalies were found.

Accident Overview

The airplane was destroyed by impact forces and subsequent fire after striking the intersection of runway 23 and runway 32 while executing a missed approach. The initial point of impact (POI) led to a wreckage path approximately 210 feet long on a heading of about 180 degrees.

Flight Crew and Duty Time

The pilot's crew day began at 1300, with a 14-hour duty limit expiring at 0300 the following morning. The second leg of the flight experienced a 1-hour-36-minute delay due to a freight delay. According to the operator, the pilot exceeded the 14-hour crew day by 45 minutes as a result of the freight delay.

Approach and Witness Accounts

The flight was cleared for the instrument landing system (ILS) approach to runway 23. A witness monitoring the Unicom radio frequency reported hearing clicking sounds, presumably to adjust runway light intensity, but no radio transmissions from the pilot. The same witness noted that ground fog was very thick. Two other witnesses reported hearing the airplane's engines, followed by a sound of the engines advancing to full power, and then the sound of impact. They observed an initial flash but, from 2,500 feet away, could not see the aircraft on fire.

Weather and Regulatory Aspects

Federal Aviation Regulation (FAR) 135.213 requires that weather observations furnished to pilots for IFR operations be made at the airport where those operations occur. The destination airport lacked authorized weather reporting, and the operator's Operating Specifications did not list an alternate weather reporting source. At 0253, weather observed 20 miles north of the airport indicated winds from 190 degrees at 4 knots, visibility 1/4 statute mile in fog, indefinite ceiling 100 feet, temperature 22°C, dew point 22°C, and altimeter setting 30.00.

Wreckage Examination

Components of the left wing were found separated. The outboard section of the left wing, beyond the engine nacelle, was located on runway 32, approximately 85 feet from the POI. Additionally, separated but unburned portions of the left aileron and left flap were recovered on the runway. The remaining pieces of the left wing were part of the main wreckage. The right wing remained attached to the main wreckage, exhibiting continuity along its entire span. Inspection of the airframe revealed no preexisting anomalies.

Probable cause

The pilot's failure to maintain control of the airplane during a missed approach. Additional factors included the operator's inadequate oversight, the pilot's improper in-flight decision, conditions conducive to pilot fatigue, fog, and night.