FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

NYC98FA071 · Piper PA-31-310

1 Mar 1998 · Presque Isle, ME, United States

Bird Air Fleet Piper PA-31-310 · Accident: in flight collision with terrain/water on approach

From Bangor International Airport (BGR) to Presque Isle International Airport (PQI)

Report a problem

Narrative check · The NTSB narrative appears to contradict this record's operation. Values are shown as recorded, not corrected; compare with the narrative.

Event

NTSB case
NYC98FA071
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 Possible conflict
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

Piper PA-31-310

Aircraft type
Piper PA-31
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
N777HM
Onboard fatalities
Unknown
Route
From Bangor International Airport (BGR), Bangor, METo Presque Isle International Airport (PQI)
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 initial 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 terrain/water
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
  • Pilot in command › Minimum descent altitude, not maintained

Approximate · Estimated position: the centre of Presque Isle, ME, the place the record names. Not the accident site.

NTSB narrative

The pilot was performing a night VOR/DME approach during which instrument meteorological conditions prevailed. The airplane was equipped with VOR, LORAN, and R-NAV receivers. There were two step-downs fixes on the approach. At 13 DME the minimum altitude was 1,800 feet. At 10 DME the minimum altitude was 1,040 feet. The missed approach point was at 6 DME, and the VOR/DME transmitter was located 5.5 miles beyond the airport. Radar data revealed a descent profile based upon distances from the end of the runway, rather than DME from the VOR. The airplane reached an altitude of 1,000 feet when it was 13.52 miles from the VOR, and 7.58 miles from the approach end of the runway. It subsequently impacted rising terrain at an altitude of about 900 feet, about 11.5 miles from the VOR, and 5.5 miles from the approach end of the runway. Impact damage and a post-crash fire precluded a check of the radio set up at the time of the accident. According to FAR 135 a pilot-in-command was required to have 1,200 hours total time. The investigation documented the pilot's total time as about 1,057 hours.

Probable cause

The pilot's failure to follow the published instrument approach procedure and his descent below the minimum descent altitude. Contributing factors were the night conditions, low ceilings, and fog.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record NYC98FA071
Event ID
20001211X09758
Case number
NYC98FA071
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: 9d8b2f15d31e587cf491bc86ac3593b30a0be9ac4f451eb2c49254b2cbedfefb; retrieved 2026-09-20T22:40:11.509Z.