# Accident 19960118000729A: Mtsbsi MU2B60, Allentown, PA, January 18, 1996

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: January 18, 1996, 19:30 local time
- Place: Allentown, PA
- Airport: Allentown-Bethlehem-Easton
- Damage: Substantial damage
- Phase of flight: Missed Approach IFR
- Operating rules: General operating rules (Part 91)
- Location: 40.5899° N, 75.4707° W: From the FAA, an estimate near the named town, within about 3 miles
- Nearby events: https://openairdocs.org/map.md?lat=40.5899&lon=-75.4707&mi=10
- Aircraft: N888TP, a cancelled registration (https://openairdocs.org/deregistered/N888TP-1997-04-25) (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
- Reported engine: GARRTT TPE33110
- People aboard: 2
- Fatal injuries: 0
- Pilot flight hours: 2,265 total, 350 in this make and model, 117 in the last 90 days
- NTSB investigation: [NTSB NYC96LA053](https://openairdocs.org/ntsb/NYC96LA053) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/19960118000729A

## Narrative

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

BROKE OUT FROM ILS APPROACH THEN REENTERED CLOUDS. DRIFTED BEGAN LATER MISSED APPROACH. HIT SNOWBANK. BELOW MINIMA.

## 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 NYC96LA053](https://openairdocs.org/ntsb/NYC96LA053), Jan 19, 1996: Mitsubishi MU-2B-6 (N888TP), Allentown, PA, substantial damage. Probable cause: the pilot's failure to comply with IFR procedures in that he attempted an instrument approach with visibility below the required minimums, and his delayed execution of a missed approach. A factor was…

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.