NYC83FA254 · Bellanca 17-31ATC
Bellanca 17-31ATC · Accident: in flight collision with terrain/water
From an unrecorded airport to Boston Logan International Airport (BOS)
Event
- NTSB case
- NYC83FA254
- 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
- 3 · 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
Bellanca 17-31ATC
- Aircraft type
- Bellanca 17
- 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
- N28077
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From not recordedTo Boston Logan International Airport (BOS), Boston, 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
- Unknown
- 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 Provincetown, MA, the place the record names. Not the accident site.
NTSB narrative
THE ACFT CRASHED IN CAPE COD BAY DURING A NIGHT X-COUNTRY FLT. TWO SECTIONS OF WOODEN WING IDENTIFIED AS FROM THE SAME MAKE AND MODEL AS THE MISSING ACFT WERE RECOVERED FROM THE BAY DURING THE 3 DAYS FOLLOWING THE FLT OF THE ACFT. OTHER IDENTIFIED PARTS OF THE ACFT WERE RECOVERED DURING THE NEXT TWO WEEKS BUT THE MAJOR PORTION OF THE WRECKAGE AND ITS 3 OCCUPANTS HAVE NOT BEEN RECOVERED. THE WEATHER WAS VMC AND THE ACFT WAS ON THE RETURN LEG OF A TRIP FROM BOSTON TO PROVINCETOWN THAT STARTED ON THE MORNING OF SEPT 11TH. THE PLT AND HIS BRIDE HAD BEEN IN BOSTON FOR 4 DAYS ON A HONEYMOON TRIP. THE ACFT DID NOT RETURN TO BOSTON AND THE COUPLES ROOM WAS NOT DISTRUBED AFTER THEY DEPARTED ON SEPT 11TH. THE ACFT MADE NO KNOWN RADIO CALLS ON THE RETURN FLT. THE COAST GUARD SEARCHED FOR TWO DAYS AFTER THE FIRST MISSING PARTS WERE FOUND ON SEPT 12TH AND AGAIN ON OCT 4TH WHEN MORE WRECKAGE WAS RECOVERED.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record NYC83FA254
- Event ID
- 20001214X44667
- Case number
- NYC83FA254
- 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: e8611513ee45faac3fbfeeab6c81a8112d4fe2318fc4a90a774f76b1d37c0324; retrieved 2026-09-21T06:10:25.706Z.