NYC01FA005 · Mitsubishi MU-2B-26A
Mitsubishi MU-2B-26A · Accident: in flight collision with object on approach
From Trenton Mercer Airport (TTN) to Martha's Vineyard Airport (MVY)
Event
- NTSB case
- NYC01FA005
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 4 · all aircraft and ground
- Ground fatalities
- 0
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Instrument Meteorological Cond
Mitsubishi MU-2B-26A
- Aircraft type
- Mitsubishi MU-2
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N60BT
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Trenton Mercer Airport (TTN), Trenton, NJTo Martha's Vineyard Airport (MVY), Edgartown, MA
- Aircraft age
- Not recorded
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 91: General Aviation
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- Approach · IFR final approach
- First occurrenceThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- In flight collision with object
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Tree(s)
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Pilot in command › IFR procedure, not followed
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot departed on a night cross-country flight without obtaining a weather briefing or flight plan. Arriving in the area of the destination airport, the weather was reported as, 2 statute miles of visibility and mist; overcast cloud layer at 100 feet. The pilot requested an instrument flight rules clearance from the approach controller, and was vectored and cleared for the ILS 24 approach. The clearance included an altitude restriction of 1,500 feet msl, until the airplane was established on the localizer. As the pilot contacted the control tower, the tower controller issued a low altitude alert to the pilot. The pilot replied that he was climbing and the tower controller cleared the pilot to land, which the pilot acknowledged. No further pertinent radio transmissions were received from the airplane. The airplane came to rest in a wooded area about 3/4-mile from the runway threshold, and about 50 feet right of the extended centerline. Review of the approach plate for the ILS 24 approach revealed that the minimum glide slope intercept altitude at the beginning of the final approach segment on the precision approach was 1,500 feet. The glide slope altitude at the final approach fix for the non-precision approach, which was located about 4 miles from the approach end of the runway, was 1,407 feet. The glide slope altitude at the middle marker, which was located about 0.6 miles from the approach end of the runway, was 299 feet. Review of radar data revealed that the airplane was observed at 700 feet, about 4 miles from the airport, and at 300 feet, about 1.5 miles from the airport. The pilot had accumulated about 1,946 hours of total flight experience, with about 252 hours in make and model. The pilot had attended initial and recurrent training for the make and model airplane; however, did not complete the training.
Probable cause
The pilot's failure to follow instrument flight procedures resulting in a collision with a tree. A factor related to the accident was the low cloud ceiling.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC01FA005
- Event ID
- 20001212X22227
- Case number
- NYC01FA005
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: local date, investigation status, coordinates. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2000-10-07.
- API snapshot SHA-256: 9871585930e8daf32577a237f5222a479a4c4fde6165b168720b86699c05e887; retrieved 2026-09-20T20:49:49.721Z.