Skip to content

Atlas / NTSB / NYC95LA135

NTSB CAROL · Event

Event NYC95LA135

1995-06-28 BRIDGEWATER, Connecticut, United States Airport · DXR None 1 aircraft Status: Completed

Registry · N9176H

FAA Aircraft Registry record.

Make / Model

CESSNA 172M

Year of manufacture

1975 · 20 years old at event

Engine

LYCOMING 0-320 SERIES (180 hp)

Seats / Engines

4 seats · 1 engine

Last airworthiness date

19750925

ADS-B equipped

Yes — Mode-S ACB3DE

Registrant of record

SKY WALKER FLIGHT SCHOOL LLC

Source: FAA Aircraft Registry (releasable master file).

Aircraft involved

Probable cause & findings

the loss of engine power for undetermined reasons resulting in a forced landing, and a subsequent collision with trees.

Factual narrative

On June 28, 1995, about 1551 eastern daylight time, a Cessna 172M, N9176H, was substantially damaged during a forced landing in Bridgwater, Connecticut. The flight instructor and commercial pilot were not injured. Visual meteorological conditions prevailed. There was no flight plan for the flight being conducted under 14 CFR Part 91. In the NTSB form 6120.1/2, the flight instructor stated that the purpose of the flight was to conduct a flight review for the commercial pilot. The local flight departed Danbury, Connecticut. An engine failure was simulated, and the commercial pilot performed the emergency procedures, while using the check list. During the recovery, when the throttle was advanced, the engine did not respond and power was not restored. The flight instructor's attempts to restore power were unsuccessful. The flight instructor performed a forced landing. During the forced landing the airplane collided with trees. Additionally, during the simulated engine failure, the carburetor heat was applied, and the throttle was advanced and retarded once. According to the Federal Aviation Administration Inspector, there were no anomalies found during a cursory inspection of the engine. Furthermore, the left and right fuel tanks contained approximately 20 and 18 gallons of fuel respectively. The engine was test run by Mattituck Airbase Inc., Mattituck, New York, under the supervision of the NTSB. During the engine test run, the engine performed at maximum power and no discrepancies were found. THE FLIGHT INSTRUCTOR WAS CONDUCTING A FLIGHT REVIEW FOR A COMMERCIAL PILOT. DURING THE FLIGHT, THE INSTRUCTOR SIMULATED AN ENGINE FAILURE. THE COMMERCIAL PILOT PERFORMED THE EMERGENCY PROCEDURES. DURING THE RECOVERY, WHEN THE THROTTLE WAS APPLIED, THE ENGINE DID NOT RESPOND. THE INSTRUCTOR'S ATTEMPTS TO RESTORE POWER WERE UNSUCCESSFUL, AND HE PERFORMED A FORCED LANDING. DURING THE FORCED LANDING, THE AIRPLANE COLLIDED WITH TREES. POSTACCIDENT EXAMINATION BY THE FAA REVEALED NO ANOMALIES. ADDITIONALLY, DURING THE ENGINE TEST RUN, THE ENGINE RAN AT FULL POWER. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12

Verbatim from NTSB's published report. Source file NTSB_1995_NYC95LA135.txt. Findings + structured fields enriched from FAA avall.mdb. Full investigation docket on data.ntsb.gov ↗.

Related research

What the literature says.

Academic papers and agency reports matching this event's aircraft type or causal vocabulary (engine failure). Sourced from NASA NTRS, NTSB Safety Studies, FAA CAMI, AOPA Air Safety Institute, Embry-Riddle Scholarly Commons, arXiv, and the Semantic Scholar academic graph.

Browse the full corpus — academia portal ↗