FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

NYC88LA154 · Bellanca 8GCBC

28 May 1988 · Kensington, NH, United States

Bellanca 8GCBC · Accident: partial loss of engine power (non-mechanical) during initial climb

From Hogan Airport (NY05) to Hampton Airfield (7B3)

Report a problem

Event

NTSB case
NYC88LA154
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
0 · 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 8GCBC

Aircraft type
Bellanca 8
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
N7672S
Onboard fatalities
Unknown
Route
From Hogan Airport (NY05), Cambridge, NYTo Hampton Airfield (7B3), Hampton, NH
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
Initial climb
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
Partial loss of engine power (non-mechanical)
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
Substantial

Cause areas

  • Pilot in command › Abort, not performed
  • Pilot in command › Carburetor heat, improper use of

Approximate · Estimated position: the centre of Kensington, NH, the place the record names. Not the accident site.

NTSB narrative

UPON REACHING THE DESTINATION AIRPORT, THE PILOT DECIDED TO DO A FEW TOUCH AND GO LANDINGS. THE AIRCRAFT TOUCHED DOWN ABOUT 600 FEET DOWNFIELD AT ABOUT 45-50 MPH. THE PILOT REPORTED THAT WITH APPLICATION OF FULL THROTTLE, THE ENGINE HESITATED. THE AIRCRAFT STARTED TO CLIMB ABOUT 400 FEET BEFORE THE END OF THE RUNWAY, HOWEVER THE CLIMB RATE WAS NOT SUFFICIENT TO CLEAR TREES 450 FEET OFF THE DEPARTURE END OF THE RUNWAY. THE AIRCRAFT CONTACTED AND SLID DOWN BETWEEN TWO TREES INVERTED.

Verbatim NTSB analysis from the NTSB dataset

Sources

NTSB record NYC88LA154
Event ID
20001213X25810
Case number
NYC88LA154
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: 4796882c3e3c6430ae2c05ff007b56093843a85ff1bfc63bea267c803d11bc89; retrieved 2026-09-23T10:11:15.479Z.