# Accident 20041130035149A: Mtsbsi MU2B60, Philadelphia, PA, November 30, 2004

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: November 30, 2004, 06:10 local time
- Place: Philadelphia, PA
- Airport: Philadelphia International
- Damage: Substantial damage
- Phase of flight: Takeoff Ground Roll
- Operating rules: Air taxi and commuter (Part 135)
- Operator: ESMA
- Location: 39.8719° N, 75.2411° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=39.8719&lon=-75.2411&mi=10
- Aircraft: N941MA, a cancelled registration (https://openairdocs.org/deregistered/N941MA-2012-01-18) (OpenAirDocs)
- Registry model: Mitsubishi MU-2B-60 (registry code 5780460, https://openairdocs.org/model/mitsubishi-mu-2b-60) (OpenAirDocs)
- Reported make and model: MTSBSI MU2B60
- People aboard: 1
- Fatal injuries: 0
- Pilot flight hours: 3,300 total, 400 in this make and model, 90 in the last 90 days
- NTSB investigation: [NTSB NYC05LA025](https://openairdocs.org/ntsb/NYC05LA025) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20041130035149A

## Narrative

As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^.

(-23) THE MU-2 WAS CLEARED FOR TAKE-OFF AT THE SAME TIME A DELTA AIRLINES TUG CREW WAS CLEARED TO CROSS THE SAME RUNWAY AT AN INTERSECTION IN THE PATH OF THE DEPARTING MU-2. LATER INVESTIGATION BY ^PRIVACY DATA OMIT^ AN AIR SSAFETY INVESTIGATOR FROM FAA HEADQUARTERS, FOUND THE CONTROLLERS TO BE AT FAULT.

## The NTSB's investigation of this event (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 NYC05LA025](https://openairdocs.org/ntsb/NYC05LA025), Nov 30, 2004: Mitsubishi MU-2B-60 (N941MA), Philadelphia, PA, substantial damage. 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…

## Other reports on N941MA (3)

Matched to the same aircraft by N-number and date.

- [Accident 20030129002539A](https://openairdocs.org/incident/20030129002539A), Jan 29, 2003: Mtsbsi MU2B60 (N941MA), Cleveland, OH, Minor damage, 1 fatal. (-23) A courier for the federal reserve bank loaded checks into the subject airlplane and then moved the van to another airplane for loading checks onto that…
- [Incident 20020115000039I](https://openairdocs.org/incident/20020115000039I), Jan 15, 2002: Mtsbsi MU2B60 (N941MA), Covington/Cinci, KY, Minor damage. (-23) On 01/15/02 N941MA, MU-2B-60, s/n 744SA, was cleared at 14 NM and 3500 MSL for the rwy 27 visual approach by cvg tower. The pilot stated he began slowing…
- [Incident 19881207064509I](https://openairdocs.org/incident/19881207064509I), Dec 7, 1988: Mtsbsi MU2B60 (N941MA), Houston, TX. Departing ramp misidentified taxi lights. Taxied off unmarked edge into ditch. Stopped in soft ground.

From the FAA Accident/Incident Data System. Reports are matched to registry aircraft by N-number and event date, checked against the reported make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. For accidents, the NTSB's own investigation is the fuller record.

---
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.