Casualties unknown

2003-11-13: Cessna 208B (N717BT) — Baltimore Air Transport, Inc./corpjet — Phoenix, AZ

Phoenix, AZ, US

On November 13, 2003, a Cessna 208B (registration N717BT) operated by Baltimore Air Transport, Inc./corpjet was involved in an aviation accident near Phoenix, AZ. Investigators recorded the probable cause as: the pilot's improper decision to taxi behind another airplane conducting an engine run-up, which resulted in a jet blast encounter. This summary draws on records from the U.S. National Transportation Safety Board (NTSB) historical archive; 8 related events involving the same aircraft type or operator are linked below.

Sourcesthe U.S. National Transportation Safety Board (NTSB) historical archivePrimary reportUpdated 1781061362Data APIEditorial standards

A Cessna 208 sustained substantial damage when it taxied behind a Bombardier CL-600 conducting a maintenance engine run-up on a cargo ramp. The area was a nonmovement area without jet blast signs. The pilot did not see a flashing beacon on the CL-600.

Incident Description

A Cessna 208 was being loaded with cargo on the south cargo ramp when it taxied behind a Bombardier CL-600 that was conducting a maintenance engine run-up. The Cessna 208 was blown up on its left wing and sustained substantial damage. The cargo ramp area where the accident occurred is considered a nonmovement area, and therefore not under the control of the control tower. There are no signs concerning jet blast in the accident area. The CL-600 was parked in a designated spot with the tail facing a blast fence.

According to the pilot of the Cessna 208, while his airplane was being loaded, he noted the CL-600 with its "tail light on" and heard it doing a run-up. He received a clearance from the ground controller to taxi from the south cargo area to runway 25L via taxiway H to H7. After getting the taxi clearance, the pilot looked and it appeared that the CL-600's run-up had been completed and the engines seemed to be at idle. As he taxied behind the CL-600, following a taxi line between the CL-600 and the blast fence, he felt his airplane buffet and heard the engines spool up. The pilot stated that he did not see the red beacon light blinking on the CL-600 prior to crossing behind it.

Witness Accounts

The maintenance crew in the CL-600 reported that they contacted PHX South Ground from the Cutter ramp and requested permission to relocate to the south cargo ramp for maintenance engine runs. After proceeding to the south cargo ramp, they had to wait for outbound traffic to park. They stated that they parked in a designated parking spot in front of the blast fence. One mechanic reported that per the normal engine run procedures, the position/navigation and beacon lights were on. Prior to performing the power assurance engine run, they verified that there were no aircraft, equipment, or personnel within "the danger zone of our engine run up." About 3 to 5 minutes into the run-up at high power, they were signaled to shut down their engines and saw the damaged airplane behind them.

Three witnesses at the southwest corner of the cargo area near the United Postal Service area reported that the CL-600 had been doing a run-up for 3 to 5 minutes prior to the Cessna 208 taxiing behind it. These witnesses all reported that they did not observe a flashing beacon light on the CL-600. Witnesses at the FedEx maintenance office observed the CL-600 conducting an engine run at high power with the rotating beacon lights on.

ATC Communications

Review of the ATC tapes disclosed that the CL-600 had been cleared to relocate to the south cargo ramp for engine test runs and that the Cessna 208 had been given a taxi clearance from the ramp without mention of the CL-600 performing engine run-ups on the ramp.

Investigation report by the U.S. National Transportation Safety Board (NTSB) historical archive. Original record: https://carol.ntsb.gov/event/20031126X01958. This page is a structured re-presentation; facts and quotes are in the National Transportation Safety Board (NTSB), United States.