Philadelphia Int'l Airport
Aircraft Accident/Incident Report

Philadelphia, Pennsylvania 19019
Tuesady, November 30, 2004 6:08 EST

NTSB Narrative Summary Released at Completion of Accident

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.

NTSB Probable Cause Narrative

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.

Event Information

Type of Event Accident
Event Date 11/30/2004
Event Day of the Week Tuesday
Time of Event 608
Event Time Zone Eastern Standard Time
Event City Philadelphia
Event State PENNSYLVANIA
Event Country --
Zipcode of the event site 19019
Event Date Year 2004
Event Date Month 11
MidAir Collision Indicator No
On Ground Collision occurred ? Yes
Event Location Latitude 395219N
Event Location Longitude 0751428W
Event Location Airport Philadelphia Int'l Airport
Event Location Nearest Airport ID PHL
Indicates whether the acc/inc occurred off or on an airport On Airport
Distance from airport in statute miles --
Degrees magnetic from airport --
Airport Elevation 36
Weather Briefing Completeness --
Investigator's weather source Weather Observation Facility
Time of the weather observation 554 Eastern Standard Time
Direction of event from weather observation facility (degrees) --
Weather Observation Facility ID PHL
Elevation of weather observation facility 36
Distance of event from weather observation facility (units?) --
Time Zone of the weather observation EST
Lighting Conditions Dawn
Lowest Ceiling Height 11000
Lowest Non-Ceiling Height --
Sky/Lowest/Cloud Conditions --
Sky Condition for Lowest Ceiling Broken
Visibility Runway Visual Range (Feet) --
Visibility Runway Visual Value (Statute Miles) --
Visibility (Statute Miles) 10
Air Temperature at event time (in degrees celsius) 3
Dew Point at event time (in degress fahrenheit) -1
Wind Direction (degrees magnetic) 0
Variable Wind Indicator Wind direction could be determined
Wind Speed (knots) --
Wind Velocity Indicator Calm
Wind Gust Indicator Not Gusting
Wind Gust (knots) --
Altimeter Setting at event time (in. Hg) 30.29
Density Altitude (feet) --
Intensity of Precipitation --
METAR weather report --
Event Highest Injury None
On Ground, Fatal Injuries --
On Ground, Minor Injuries --
On Ground, Serious Injuries --
Injury Total Fatal --
Injury Total Minor --
Injury Total None 1
Injury Total Serious --
Injury Total All --
Investigating Agency NTSB
NTSB Docket Number (internal use) 19265
NTSB Notification Source PHL FSDO
NTSB Notification Date Nov 30 2004 12:00AM
NTSB Notification Time 815
Fiche Number and/or location -used to find docket information DMS
Date of most recent change to record Feb 28 2006 12:35PM
User who most recently changed record NTSB\JOHB
Basic weather conditions Visual Meteorological Cond
FAA District Office Philadelphia FSDO

Aircraft Involved

Aircraft #1

Aircraft Registration Number N941MA
NTSB Number NYC05LA025
Missing Aircraft Indicator --
Federal Aviation Reg. Part Part 135: Air Taxi & Commuter
Type of Flight Plan filed IFR
Flight plan Was Activated? Yes
Damage Substantial
Aircraft Fire None
Aircraft Explosion None
Aircraft Manufacturer's Full Name Mitsubishi
Aircraft Model MU-2B-60
Aircraft Series Identifier --
Aircraft Serial Number 744 SA
Certified Max Gross Weight 11575
Aircraft Category Airplane
Aircraft Registration Class --
Aircraft is a homebuilt? No
Flight Crew Seats --
Cabin Crew Seats --
Passenger Seats --
Total number of seats on the aircraft 3
Number of Engines 2
Fixed gear or retractable gear Retractable
Aircraft, Type of Last Inspection --
Date of Last Inspection --
Airframe hours since last inspection --
Airframe Hours --
ELT Installed Yes
ELT Activated No
ELT Aided Location of Event Site No
ELT Type --
Aircraft Owner Name EPPS AIR SERVICE INC
Aircraft Owner Street Address --
Aircraft Owner City Atlanta
Aircraft Owner State GA
Aircraft Owner Country USA
Aircraft Owner Zipcode 30341
Operator is an individual? No
Operator Name --
Operator Same as Owner? Yes
Operator Is Doing Business As --
Operator Address Same as Owner? Yes
Operator Street Address --
Operator City --
Operator State --
Operator Country --
Operator Zip code --
Operator Code ESMA
Owner has at least one certificate None
Other Operator of large aircraft? --
Certified for Part 133 or 137 Operation --
Operator Certificate Number --
Indicates whether an air carrier operation was scheduled or not Non-scheduled
Indicates Domestic or International Flight Domestic
Operator carrying Pax/Cargo/Mail Cargo
Type of Flying (Per_Bus / Primary) --
Second Pilot on Board No
Departure Point Same as Event Yes
Departure Airport Code PHL
Departure City Philadelphia
Departure State PA
Departure Country USA
Departure Time 600
Departure Time Zone EST
Destination Same as Local Flt --
Destination Airport Code TEB
Destination City Teterboro
Destination State NJ
Destination Country USA
Specific Phase of Flight Takeoff - aborted
Report sent to ICAO? No
Evacuation occurred No
Date of most recent change to record Nov 12 2005 5:00PM
User who most recently changed record MUZD
Since inspection or accident --
Event Location Runway Number and Location 35
Runway Length 5460
Runway Width 150
Sight Seeing flight No
Air Medical Flight No
Medical Flight --