Accident Mitsubishi MU-2B-60 N941MA,
ASN logo
ASN Wikibase Occurrence # 294322
 
This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information. If you feel this information is incomplete or incorrect, you can submit corrected information.

Date:Tuesday 30 November 2004
Time:07:08 LT
Type:Silhouette image of generic MU2 model; specific model in this crash may look slightly different    
Mitsubishi MU-2B-60
Owner/operator:Epps Air Service Inc
Registration: N941MA
MSN: 744 SA
Year of manufacture:1979
Engine model:Garrett TPE 331
Fatalities:Fatalities: 0 / Occupants: 1
Aircraft damage: Substantial
Category:Accident
Location:Philadelphia, Pennsylvania -   United States of America
Phase: Unknown
Nature:Unknown
Departure airport:Philadelphia International Airport, PA (PHL/KPHL)
Destination airport:Teterboro Airport, NJ (TEB/KTEB)
Investigating agency: NTSB
Confidence Rating: Accident investigation report completed and information captured
Narrative:
The airplane collided with a tug during takeoff. According to the pilot of the MU-2 airplane he was cleared to taxi from his parking spot on the northeast side of the airport, to runway 35, by the ground controller on duty. He then taxied to runway 35 via taxiway A, taxiway D, across runway 26, to taxiway K. Approximately 1 minute after the pilot of the MU-2 was cleared to taxi, the same ground controller cleared a maintenance tug towing an MD-80, to taxi from the same (northeast) ramp as the MU-2, to a ramp on the west side of runway 35. The taxi clearance issued by the ground controller included a clearance for the tug to cross runway 35. Once the MU-2 pilot arrived at the runway, he contacted the tower controller and was cleared for takeoff from runway 35. The pilot initiated a takeoff, and as the airplane reached an airspeed of 80 knots, the pilot observed an aircraft tug crossing the runway centerline. The pilot then aborted the takeoff, and maneuvered the airplane to the left side of the runway; however, the airplane contacted the tug at the intersection of runway 35 and taxiways "Golf" and "Echo." At the time of the accident, three full performance level air traffic controllers were working in the tower cab; a local controller (LCE), ground controller (GC), and clearance delivery controller. The LCE and GC positions were located next to each other in the northeast corner of the tower cab. FAA Air Traffic Control regulations required that a ground controller must obtain approval from a local controller before authorizing an aircraft or a vehicle to cross or use any portion of an active runway. Additionally, the standard operating procedures for the airport required all runway crossing authorization and runway crossing complete coordination to be accomplished via a recorded landline. Controller interviews and review of recorded voice communications revealed the ground controller did not coordinate the runway crossing of the maintenance tug with the local controller.

Probable Cause: The failure of the ground controller to coordinate the runway crossing of a maintenance tug, with the local controller, which resulted in a ground collision with an MU-2 airplane during it's takeoff roll.

Accident investigation:
cover
  
Investigating agency: NTSB
Report number: NYC05LA025
Status: Investigation completed
Duration: 1 year and 3 months
Download report: Final report

Sources:

NTSB NYC05LA025

Revision history:

Date/timeContributorUpdates
11-Oct-2022 15:14 ASN Update Bot Added

Corrections or additions? ... Edit this accident description

The Aviation Safety Network is an exclusive service provided by:
Quick Links:

CONNECT WITH US: FSF on social media FSF Facebook FSF Twitter FSF Youtube FSF LinkedIn FSF Instagram

©2024 Flight Safety Foundation

1920 Ballenger Av, 4th Fl.
Alexandria, Virginia 22314
www.FlightSafety.org