FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

NYC96LA096 · Cessna 152

5 May 1996 · HARWINTON, CT, United States

Atlantic Air Cessna 152 · Accident: total loss of engine power (non-mechanical) during initial climb

From 22B to an unrecorded destination

Report a problem

Event

NTSB case
NYC96LA096
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

Cessna 152

Aircraft type
Cessna 152
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
N25414
Operator
Atlantic Air
Onboard fatalities
Unknown
Route
From 22BTo 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
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
Total 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
Fuel contamination; Wire, transmission
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

  • Airport facilities, fuel storage › Inadequate
  • Company/operator management › Preflight planning/preparation, inadequate
  • Fluid, fuel › Contamination, water
  • Maintenance › Inadequate

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

NTSB narrative

Water was found in the fuel tanks during preflight, and additional draining was accomplished until no more water appeared. The pilots boarded the airplane and initiated a takeoff, at which time, the engine sputtered, and the takeoff was aborted. After the airplane cleared the runway, the engine lost total power; attempts to restart it were unsuccessful. The airplane was pushed to the operator's hangar where the operator inspected the airplane. Additional water was found in the tanks, which was drained, then the engine was run. The operator said the airplane was, '...OK to fly...', and the pilots boarded the airplane for departure. Once they were airborne, about 200 feet high, the engine lost power. During the forced landing, the airplane struck a power line and descended to the ground where it nosed over. When the airplane was placed upright, additional water was found in the tanks. Examination of the fuel farm, where the airplane was refueled, revealed the filter was collapsed, and the fuel was contaminated with water. The FAA reported the operator did not have a fuel management program in place or the appropriate equipment to maintain a fuel farm. According to the airplane manufacturer, '...If excessive sampling is required, the recommended procedure is to completely defuel, drain and clean the airplane fuel system, and attempt to discover where and how the contamination originated before the airplane flys again....'

Probable cause

the operator's failure to eliminate water-contaminated fuel from the airplane, which resulted in the loss of engine power and collision with an obstacle during the forced landing. Also causal was an improperly maintained fuel storage facility.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record NYC96LA096
Event ID
20001208X05846
Case number
NYC96LA096
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: ac66c95148db9014d94310ac1a5e5a805b0bb41427b793987c3bee849151359b; retrieved 2026-09-21T21:52:13.688Z.