FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

NYC84FA189 · Taylorcraft BC12-D

9 Mar 1984 · South Paris, ME, United States

Taylorcraft BC12-D · Accident: in flight collision with terrain/water en route

From Bowdoinham, ME to an unrecorded destination

Report a problem

Event

NTSB case
NYC84FA189
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
1 · 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

Taylorcraft BC12-D

Aircraft type
Taylorcraft BC12
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
N95040
Operator
Unknown
Onboard fatalities
Unknown
Route
From Bowdoinham, METo not recorded
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
En route · descent
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

  • Reason for occurrence undetermined

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

NTSB narrative

BEFORE THE ACCIDENT, THE PLT WAS LAST SEEN ON 3/9/84 AT 1530 EST & HAD NOT EXPRESSED ANY INTENTIONS OF FLYING. AT 1730, HIS CAR WAS LOCATED AT THE ARPT & HIS ACFT, WHICH HAD BEEN KEPT THERE, WAS GONE. THE ACFT WAS FOUND ON 5/24/84 WHERE IT HAD CRASHED ON MOUNTAINOUS/HILLY TERRAIN WHILE DESCENDING UNDER UNKNOWN CIRCUMSTANCES. THE HISTORY OF FLT COULD NOT BE DETERMINED. NO EVIDENCE OF A PREIMPACT MECHANICAL MALFUNCTION OR FAILURE OF THE ACFT WAS FOUND. A TOXICOLOGICAL CHECK OF THE PLT'S BLOOD REVEALED AN ALCOHOL LEVEL OF 0.08%; HOWEVER, THE AMOUNT OF ALCOHOL DUE TO PUTREFACTION WAS NOT KNOWN. ABOUT 45 MI SE OF THE ACCIDENT SITE, THE 1650 EST WX AT PORTLAND, ME, WAS, IN PART: SKY CLEAR, VISIBILITY 20 MI, WIND 030 DEG AT 10 KTS.

Verbatim NTSB analysis from the NTSB dataset

Sources

NTSB record NYC84FA189
Event ID
20001214X39147
Case number
NYC84FA189
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: 505c36aaabc026b669e3944447c38d18f07a54b6e5a02d90e29cb469fca3fbd2; retrieved 2026-09-21T05:37:19.768Z.