# NTSB LAX04LA043: Cessna 208B, N717BT, Phoenix, AZ, November 13, 2003 - Type: NTSB accident investigation - Classification: Accident · No injuries · Limited investigation · Final report - Date: November 13, 2003, 06:47 local (13:47 UTC) - Place: Phoenix, AZ - Coordinates: 33.434722, -112.013336 - Nearby events: https://openairdocs.org/map.md?lat=33.4347&lon=-112.0133&mi=10 - Phase of flight: [Taxi](https://openairdocs.org/ntsb-phases/250) (OpenAirDocs' grouping) - Highest injury: No injuries - Injuries: 1 uninjured - Status: Completed, report April 25, 2006 - Report: Approved by Office Director - Parties: Federal Aviation Administration (PHX CMO) - NTSB case key (mKey): 58346 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=LAX04LA043 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/58346/pdf - Page: https://openairdocs.org/ntsb/LAX04LA043 ## Probable cause the pilot's improper decision to taxi behind another airplane conducting an engine run-up, which resulted in a jet blast encounter. ## Sequence of events In NTSB's coding before 2008 (https://www.ntsb.gov/GILS/Documents/codman.pdf). - Propeller blast or jet exhaust/suction, taxi - to takeoff - in-flight planning/decision - inadequate, pilot in command (cause) - wrong taxi route - selected, pilot in command (cause) ## Analysis The airplane taxied behind a Bombardier CL-600 that was conducting a maintenance engine run-up and 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's statement, while his airplane was being loaded with cargo he noted 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. The pilot said that after getting his taxi clearance he 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. According to the maintenance crew in the CL-600, 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. The maintenance crew 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 shutdown their engines and saw the damaged airplane behind them. Three witnesses at the southwest corner of the cargo area, near the United Postal Service (UPS) 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 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. 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. ## Factual narrative On November 13, 2003, at 0647 mountain standard time, a Cessna 208B, N717BT, was blown over by a Bombardier, Inc., CL-600-2024, N905J, while taxiing to the active runway from the south cargo area at the Phoenix Sky Harbor International Airport (PHX), Phoenix, Arizona. Tarene Leasing LLC, d.b.a. Baltimore Air Transport/ CorpJet and contracted out to Federal Express (FedEx), operated the airplane (N717BT) under the provisions of 14 CFR Part 135 as a cargo flight. The airplane sustained substantial damage. The commercial pilot, the sole occupant was not injured. The Mesa Airlines Bombardier CL-600-2024 (N905J) was being run-up as part of a maintenance activity and was not damaged. The maintenance crew was not injured. Visual meteorological conditions prevailed for the flight and an instrument flight rules (IFR) flight plan had been filed. According to the pilot of the N717BT, while his airplane was being loaded with cargo he noted N905J with its "tail light on" and heard it doing a run-up. He received a clearance from PHX ground at the south cargo area to taxi to runway 25L via taxiway H to H7. After picking up his taxi clearance he reported that the run-up had been completed and the CL-600 seemed to be at idle. As he taxied behind N905J he felt his airplane "buffet, and heard the engines [spool] up." The pilot stated that he did not see the red beacon light blinking, indicating that the engines were running, prior to crossing behind the tail end of N905J. According to the maintenance crew of N905J, they contacted PHX South Ground (frequency 132.55) at 0620 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. The maintenance crew 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 shutdown their engines. They reduced the power to idle and began to look out the windows to see what the problem was. When they saw people at the rear of the airplane they shut the engines down completely and when they exited the airplane saw that N717BT had been damaged. Three witnesses at the southwest corner of the cargo area, near the United Postal Service (UPS) area reported that N905J had been doing a run-up for 3 to 5 minutes prior to N717BT taxiing behind it. Once N717BT taxied behind N905J it went up on its left wing until the pilot of N905J was signaled to shut the engines down, at which point N717BT came to rest on its main landing gear. The witnesses all reported that they did not observe a flashing beacon light on N905J. Another witness at the cargo ramp reported that he observed N905J doing a run-up with its rotating beacon lights off. Witnesses at the FedEx maintenance office observed N905J conducting an engine run at high power with the rotating beacon lights on. They observed N717BT taxi behind N905J and start "rocking violently" when it went up on its wing and stayed there until FedEx crew was able to signal the maintenance crew of N905J to shutdown the engines. According to a Federal Aviation Administration (FAA) inspector, the cargo area is considered a nonmovement area, and therefore, not under the authority of the control tower. He also reported that there were no signs concerning jet blast in the accident area. The inspector examined the accident airplane on scene. He noted that the left wing was bent up at a 45-degree angle about 6 feet inboard from the wingtip. According to the FAA inspector, the CL-600's engines' exhausts were facing towards the blast fence. There was a taxi line behind the CL-600 and the blast fence, which the Cessna utilized while taxiing to the active runway. A review of the audiotapes from PHX tower indicated that the maintenance crew of N905J contacted the controller for the south ground position and requested a clearance to reposition to the south cargo ramp to conduct engine runs. The controller cleared N905J to the south cargo ramp. A Notice to Airmen (NOTAM) #294-2003, issued on October 29, 2003, stated: Effective Wednesday, October 29, 2003, at 1400 (L) hours, aircraft engine run-up request should be directed to the operations airside supervisor via FAA tower. Location will be determined by prevailing wind and airfield conditions. ## Aircraft - Registration: [N717BT](https://openairdocs.org/deregistered/N717BT-2005-09-29), registration cancelled 2005-09-29, S/N 208B0863, built 2000 (OpenAirDocs) - Reported make and model: Cessna 208B - Registry model: [Cessna 208B](https://openairdocs.org/model/cessna-208b) (registry code 2073701) (OpenAirDocs) - Registry engine: [Pratt & Whitney PT6A series](https://openairdocs.org/engine/pratt-whitney-pt6a-series) (registry code 52032, turbo-prop) (OpenAirDocs) - Category: Airplane - Serial number: 208B0863 - Airframe hours: 2349.8 - Engines: Pratt & Whitney PT6114A 675 horsepower turbo prop - Damage: Substantial damage - Flight: Part 135 - Operator: Baltimore Air Transport, Inc./CorpJet, doing business as Baltimore Air Transport, Inc./CorpJet - Registered owner: Tarene Leasing LLC - Airworthiness certificate: Standard, Normal - Last inspection: 100 hour, October 1, 2003, 20 hours before - Departed: PHX, PHOENIX, AZ - Destination: SOW, Showlow, AZ - Flight plan: IFR - Airport: PHX, Phoenix Sky Harbor Intl ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 30; injuries: none; airline transport; airplane ratings: single-engine land, multi-engine land; instrument ratings: airplane; medical: class 1; last flight review October 1, 2003; seat: left; flight hours: 2,850 total, 350 in this make and model, 2,300 as pilot in command ## Weather - Conditions: Visual (VMC), Day - Wind: 280° at 5 knots - Visibility: 10 statute miles - Lowest ceiling: 6,000 ft broken - Temperature: 61 °F, dew point 57 °F - Altimeter: 30.05 inHg - Observed at: PHX ## FAA reports on this event (1) The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs). - [Accident 20031113029279A](https://openairdocs.org/incident/20031113029279A), Nov 13, 2003: Cessna 208B, Phoenix, AZ, Substantial damage. (-23) While training out of the south cargo area @ phx, the pilot encountered the jet blast from a regional jet running up on the ramp. The sudden jet blast… ## Other investigations on N717BT (1) From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. - [NTSB LAX05LA244](https://openairdocs.org/ntsb/LAX05LA244), Jul 22, 2005: Cessna 208B (N717BT), Globe, AZ, substantial damage. Probable cause: The fatigue failure of the compressor turbine stator vane, the liberation of vane material into the compressor turbine, and the total loss of engine power. Also causal was the operator's failure to… From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. --- OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.