Premium research interface

The modern interface for aviation safety intelligence.

Search investigations, review source evidence, monitor watched reports, and trace long-term patterns from one calm, data-first workspace.

63k+
Reports indexed
1940-2026
Coverage
Recent
Last data refresh
Featured Report

Loading…

Loading featured report…

Loading…
Open Report

Safety trends by operating rule

Track fatal and non-fatal accident patterns across Part 91, Part 135, and Part 121 operations.

Loading trend charts…

Browse the aviation graph

Move quickly by aircraft, airport, operator, and time with indexes built for research, not wandering.

Last Data Update

By Decade

By Month

Aircraft Manufacturer

More manufacturers

Airports

More airports

Operators

More operators

About

Aviation safety reports, made easier to study

NTSB Reports is an independent research and search tool for public aviation accident and incident records. It brings NTSB aviation reports, structured fields, docket files, extracted figures, photos, videos, and update history into one searchable interface.

The goal is practical safety education: make it faster to find relevant investigations, compare similar events, review factual records, and understand the evidence behind probable-cause and preliminary reports.

The investigative work and source records belong to the National Transportation Safety Board and the published investigation record. This site is not affiliated with or endorsed by the NTSB.

FAQs

NTSB Report

August 31, 2012 · Cessna 172M · N391R

Canadensis, PA

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
August 31, 2012
Injury Outcomes
No injuries (2 uninjured)
Location
Canadensis, PA
Aircraft
Cessna 172M
Tail Number
N391R
Operator
Kurtz Andrew D
Injuries
None
Aircraft Damage
Substantial
NTSB Number
ERA12LA539

The pilot performed a preflight inspection of the airplane and an engine run-up with no discrepancies reported before departing. He departed with an adequate supply of fuel and proceeded toward his destination airport. During cruise flight, with the fuel-to-air ratio leaned, the pilot heard an engine sound that he said was similar to a cylinder not firing; the engine then experienced significant vibration and a partial loss of power. Attempts to restore engine power were unsuccessful. The flight was vectored by an air traffic controller to the Cherry Ridge Airport (N30), and on the first approach to the 2,405-foot-long grass downsloping runway designated 20, the flight was high and fast resulting in a bounced landing necessitating a go-around. He executed a 180 degree turn to land on runway 2, and while on final approach, the airplane was allowed to descend below the elevation of the runway resulting in undershoot followed by a nose-over. While the postaccident inspection of the engine revealed a discrepancy with one magneto and very low compression from the No. 4 cylinder, the pilot stated that his in-flight check of each magneto revealed satisfactory results.

NTSB Probable Cause

Aircraft-Aircraft power plant-Engine (reciprocating)-Recip eng cyl section-Malfunction - F

Full Narrative

On August 31, 2012, about 1145 eastern daylight time, a Cessna 172M, N391R, registered to and operated a private individual, landed short of the intended runway during a precautionary landing at Flying Dollar Airport, Canadensis, Pennsylvania. Visual meteorological conditions prevailed at the time no flight plan was filed but visual flight rules (VFR) flight following was being provided for the 14 Code of Federal Regulations (CFR) Part 91 personal flight from Princeton Airport (39N), Princeton/Rocky Hill, New Jersey, to Cherry Ridge Airport (N30), Honesdale, Pennsylvania. The airplane sustained substantial damage, and there were no injuries to the private pilot, one passenger, or a dog. The flight originated from 39N about 1110. The pilot stated that the purpose of the flight was pleasure, and the estimated flight time from 39N to N30 was 52 minutes. He performed a preflight inspection of the airplane using a checklist which included using a dipstick to check the quantity of fuel in each tank, and also checking the wing fuel tanks and fuel strainer for contaminants; none were found. The left tank had about 10 gallons and the right fuel tank had about 12 gallons; both tanks contained 100 low lead (100LL) fuel. He also checked the engine oil which indicated 6.1 quarts and added 1.0 quart. Prior to departure he performed an engine run-up which included checking the magnetos. Each magneto drop was about 50 rpm. The flight departed with the fuel selector positioned to both, proceeded due North towards the destination and climbed to 4,500 feet while obtaining VFR flight following. After reaching cruise altitude, or about 5 to 10 minutes into the flight, he reduced throttle, leaned the fuel to air ratio until the engine ran rough, then enriched it slightly. Some time later, the engine sound changed but was not a loud sound. The sound he described was more like a cylinder not firing. There was significant vibration, and he ran the emergency procedures by verifying the primer was in and locked, the fuel selector was on both, placed the mixture control to full rich, then a short time later checked the magnetos noting the engine continued to run on any selection (left, right, and both). He also reported adding carburetor heat, but nothing he did corrected the situation. Since the engine was still developing some power he declared PAN PAN PAN with the controller who vectored the flight to 8N4. At that time the flight was about 6.5 miles east of there, and 3,000 feet above the field elevation. He flew towards 8N4, and with the engine still developing partial power, the controller advised him of the orientation of the runway 02/20. The wind favored runway 20, so he continued to the airport and minimized his loss of altitude. He noted that the vibration increased with decreased engine rpm, so he set the power about midrange. He flew left base to final for runway 20 (which is a 2,405 foot long grass runway) and with no flaps extended performed an aggressive forward slip to lose altitude because the flight was high. The airplane touched down a little fast, bounced a couple times, and he added some power to correct the bounce. With the end of the runway coming near and a terrain drop near the end of runway 20, he performed a go-around. He executed a 180 degree turn to land on runway 02, and on final approach the plane was 10 to 15 feet below the altitude of the runway. He pulled back on the yoke, and while flying at 40 miles-per-hour, impacted 45 degree upsloping terrain. The airplane nosed over and then all occupants exited the airplane. He later reported that at no point before touchdown did the engine quit or the propeller stop. The pilot later stated that postaccident, he went back to the airport and noticed for the first time that runway 20 is downsloping. He also stated that the airport owner acknowledged this and because of that fact, said landings are usually on runway 02, and departures are from runway 20. A postaccident examination of the airplane and engine was performed by a Federal Aviation Administration (FAA) airworthiness inspector following recovery of the airplane. Inspection of the airplane revealed an adequate fuel supply remaining with no contamination noted; the fuel strainer still had fuel inside. Examination of the engine revealed crankshaft, camshaft, and valve train continuity; no stuck valves were noted. During hand rotation of the engine, no detectable compression was noted at the No. 4 cylinder (leakage past the exhaust valve was detected). The magnetos were tightly installed and properly timed to the engine; however, one magneto “…had very little spark” during hand rotation of the engine. The bottom spark plugs were noted to be oil soaked. The fuel and air induction systems of the engine checked satisfactory. With respect to the engine, the pilot reported having to lean the fuel/air ratio to burn off carbon etc., from the spark plugs.

Flight

Event TypeAccident
Event Time11:45 EDT
Nearest AirportFlying Dollar Airport (0nm)
Runway02
Runway Length2405 ft
Runway Width100 ft
Flight Plan FiledNone
Flight Plan ActivatedNo
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftCessna 172M
Tail NumberN391R
Aircraft CategoryAir
DamageSubstantial
OperatorKurtz Andrew D
Operating RulePart 91
Engines1
Engine TypeReciprocating
Engine DetailsLycoming · O-320-E2D · Reciprocating · 150
Seats4

People & Injuries

Injury SummaryNo injuries (2 uninjured)
Fatal0
Serious0
Minor0
Uninjured2
Total2
Crew 1Age 58 · Third Class · None

Conditions

ConditionsVMC
LightDaylight
Wind250° @ 10 kt
Visibility10 sm
CeilingNone
Temperature / Dew Point55
Altimeter30.05 inHg
Observation Time15:54
Weather SourceWFAC

Appendix: Source Data