FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

NYC00FA064 · Aerostar 601P

10 Jan 2000 · Coatesville, PA, United States

Aerostar 601P · Accident: in flight collision with object on approach

From Millville Municipal Airport (MIV) to 40N

Report a problem

Event

NTSB case
NYC00FA064
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
2 · 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
Visual Meteorological Cond

Aerostar 601P

Aircraft type
Aerostar 601
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
N905DK
Operator
Unknown
Onboard fatalities
Unknown
Route
From Millville Municipal Airport (MIV), Millville, NJTo 40N
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
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 › Climb, not obtained
  • Pilot in command › IFR procedure, not followed

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

While operating in IMC, the pilot was vectored to the final approach course for an ILS approach. Weather at the airport was ceiling 200 feet and visibility 3/4 mile in mist. The pilot was cleared for the approach, which he acknowledged. No other transmissions were received from the accident airplane. Radar data showed the airplane intercept the final approach course, then track inbound. The airplane crossed the outer marker 420 feet below the glide slope. The last radar return showed the airplane at 440 feet agl, 3.9 miles from the runway. The airplane impacted the ground at a shallow angle about 1 mile north of the airport on the opposite side of the missed approach procedure. The elevation of the accident site was approximately 40 feet lower than the airport. The pilot had about 350 hours of total flight experience. No pre-impact failures were identified with the airframe, engines, flight controls, or flight instruments.

Probable cause

The pilot's failure to follow the published instrument approach procedure, and his failure to establish a climb after passing the missed approach point.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record NYC00FA064
Event ID
20001212X20422
Case number
NYC00FA064
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: investigation status. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: 646ef7d4a56ad94f1eff45d2fddc74be1b930df65ffa393b9e8b53f3cf772b3d; retrieved 2026-09-20T21:31:03.151Z.