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 19, 2000 · Cessna 152 · N67495

Culpeper, VA

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
August 19, 2000
Injury Outcomes
No injuries (1 uninjured)
Location
Culpeper, VA
Aircraft
Cessna 152
Tail Number
N67495
Injuries
None
Aircraft Damage
Substantial
NTSB Number
NYC00LA234

The student pilot departed the airport for the last leg of the solo cross-country flight. About 50 feet above the runway, the engine RPMs suddenly and smoothly dropped to an estimated 1700 RPMs, 'as if the throttle was being pulled back.' The student pilot advanced and retarded the throttle several times; however, the engine maintained a constant speed of 1700 RPMs. He pulled the mixture to the cut-off position, and performed an emergency landing in a field. Examination of the airplane revealed the throttle linkage had become disconnected from the throttle. The linkage was reconnected and the engine was started. While the engine was running, the linkage was disconnected again, and the engine RPMs decreased to 1500 RPMs. The last annual inspection was performed on April 21, 2000, and the airplane had accumulated 79 flight hours since then.

NTSB Probable Cause

The partial loss of power due to an inadequate annual inspection, which resulted in the throttle linkage becoming disconnected from the throttle.

Full Narrative

On August 19, 2000, at 1715 Eastern Daylight Time, a Cessna 152, N67495, was substantially damaged during a forced landing after takeoff from Culpeper Regional Airport (CJR), Culpeper, Virginia. The certificated student pilot was not injured. Visual meteorological conditions prevailed and no flight plan was filed for the solo cross country flight conducted under 14 CFR Part 91. The pilot departed from Shannon Airport (EZF), Fredricksburg, Virginia, for a "round robin" cross-country flight. He planned to stop at the Farmville Regional Airport, the Louisa County Airport, the Culpeper Regional Airport, and then return to EZF. According to the pilot's written statement, he said: "The entire flight, up to and including the landing at Culpeper, went as planned. After landing on runway 04 at Culpeper, I back-taxied on runway 04 for departure on that runway. After back taxing, I checked the fuel shut off valve, all of the flight instruments, and all of the electrical components. Everything was normal. I went to full throttle and began rolling down runway 04. I lifted off and began climbing at 70 knots. At approximately 50 feet off the runway the engine RPMs suddenly, rapidly, and smoothly dropped to an estimated 1700 RPMs. I immediately tried to retard the throttle fully so that I could land back on runway 04 but there was no response. The RPMs were stuck at about 1700. There was not enough power to climb and too much power to land. The runway was now behind me and I realized I would have to make an emergency landing. I pulled the mixture to lean/cut off, announced my intentions to Culpeper traffic, and made an emergency landing in the field beyond runway 04. I rolled for approximately 100 feet before the nose gear hit a hole." In a subsequent telephone interview, the pilot described the partial power loss "as if the throttle was pulled back." The pilot reported there was no "coughing," or "backfiring," associated with the power reduction. The engine maintained a constant speed of 1700 RPMs, despite the pilots attempts to advance and retard the throttle. Additionally, the pilot turned the fuel selector and the master switch to their "off" positions before exiting the airplane. An on-scene examination of the airplane by a Federal Aviation Administration (FAA) inspector revealed no fuel in the fuel strainer, sump drain, or carburetor; however, both fuel tanks were "about half full." The FAA inspector observed no obstructions or leaks in the fuel lines. Additionally, it was noted that the throttle linkage had become disconnected from the throttle. The attaching hardware was not found. The airplane was removed from the accident site and examined further at a hangar. The throttle linkage was reconnected to the throttle and 3 to 5 gallons of fuel was added to the fuel tank. The engine started and fuel was observed in the shut-off valve, fuel strainer, and carburetor. The throttle was then increased to 2000 RPM, and the fuel selector was turned to the "off" position. The engine stopped producing power "almost immediately." The engine was then restarted, the inspector disconnected the throttle linkage from the throttle, and the engine ran at about 1500 RPM. According to the FAA inspector, an annual inspection was performed on the airplane on April 21, 2000. Since the inspection, the airplane had flown about 79.6 hours.

Flight

Event TypeAccident
Event Time17:15 EDT
Nearest AirportCulpeper Regional Airport (0nm)
Runway4
Runway Length4002 ft
Runway Width75 ft
Flight Plan FiledNone
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftCessna 152
Tail NumberN67495
Aircraft CategoryAir
DamageSubstantial
Operating RulePart 91
Engines1
Engine TypeReciprocating
Engine DetailsLycoming · O-235 · Reciprocating · 110
Seats2

People & Injuries

Injury SummaryNo injuries (1 uninjured)
Fatal0
Serious0
Minor0
Uninjured1
Total1
Crew 1Age 23 · Third Class

Conditions

ConditionsVMC
LightDaylight
Wind10° @ 7 kt
Visibility10 sm
CeilingBroken clouds 5000 ft
Temperature / Dew Point63 F
Altimeter30.00 inHg
Observation Time21:23
Weather SourceWFAC

Appendix: Source Data