# Accident 20000819039219A: Cessna 152, Culpeper, VA, August 19, 2000

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: August 19, 2000, 17:15 local time
- Place: Culpeper, VA
- Airport: Culpeper Regional Airport
- Damage: No damage
- Operating rules: General operating rules (Part 91)
- Location: 38.4693° N, 78.0003° W: From the FAA, an estimate near the named town, within about 3 miles
- Nearby events: https://openairdocs.org/map.md?lat=38.4693&lon=-78.0003&mi=10
- Aircraft: N67495, registered now (https://openairdocs.org/aircraft/N67495) (OpenAirDocs)
- Registry model: Cessna 152 (registry code 2071835, https://openairdocs.org/model/cessna-152) (OpenAirDocs)
- Registry engine: Lycoming 0-235 series (registry code 41505, https://openairdocs.org/engine/lycoming-0-235-series) (OpenAirDocs)
- Reported make and model: CESSNA 152
- Pilot certificates: Student
- NTSB investigation: [NTSB NYC00LA234](https://openairdocs.org/ntsb/NYC00LA234) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20000819039219A

## Narrative

As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^.

(-23) ON AUGUST 19, 2000, AT 1715 EDT, A CESSNA 152, N67495, WAS SUBSTANTIALLY DAMAGED DURING A FORCED LANDING AFTER TAKEOFF FORM 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.  AFTER LANDIGN AT CJR, THE PILOT COMPLETED THE AFTER-LANDIND AND BEFORE TAKEOFF CHECKLIST AND TAXIED BACK TO RUNWAY 9 FOR DEPARTURE. HE ADVANCED THE THROTTLE TO FULL POWER AND DURING THE TAKEOFF ROLL HE NOTICED NO ABNORMALITIES OF THE ENGINE GAUGE INDICATIONS.  AS THE AIRPLANE REACHED AVOUT 40 FEET ABOVE THE GROUND, IT EXPERIENCED A REDUCTION IN POWER, "AS IF THE THROTTLE WAS PULLED BACK".  THE PILOT REPORTED THERE WAS NO COUGHING OR BACKFIRING ASSOCIATED WITH THE POWER REDUCTION, AND THE ENGINE MAINTAINED A CONSTANT SPEED OF 1700 RPM'S.  THE PILOT RETARDED THE THROTTLE IN AN ATTEMPT TO LAND ON THE REMAINING RUNWAY; HOWEVER, HE RECEIVED NO RESPONSE FROM THE ENGINE.  HE ADVANCED AND RETARDED THE THROTTLE SEVERAL TIMES AS THE ENGINE POWER  REMAINED CONSTANT AT 1700 RPM'S.  THE PILOT THEN PULLED BACK THE MIXTURE CONTROL   TO "REDUCE THE AIRPLANE'S POWER" AND PERFORMED A FORCED LANDING IN A FIELD.  DURING THE LANDING ROLLOUT THE AIRPLANE IMPACTED A HOLE AND TIPPED ON ITS NOSE. THE PILOT TURNED THE FUEL SELECTOR AND THE MASTER SWITCH TO THEIR OFF POSITIONS BEFORE EXITING THE AIRPLANE. EXAMINATION OF THE AIRPLANE REVEALED NO FUEL IN THE FUEL STRAINER, SUMP DRAIN, OR CARBURETOR; HOWEVER, BOTH FUEL TANKS WERE ABOUT HALF FULL.  NO OBSTRUCTIONS OR LEAKS WERE ABSERVED IN THE FUEL LINES.  ADDITIONALLY, IT WAS NOTED THAT THE THROTTLE LINKAGE HAD BECOME DISCONNECTED FROM THE CARBURETOR.  FURTHER EXAMINATION OF THE SIGHT AND OF THE AIRCRAFT ENGINE CARBURETOR DID NOT REVEAL THE CARBURETOR LINKAGE BOLT.  THE AIRCRAFT ENGINE WAS RUN AT A REPAIR STATION AND PERFORMANCE WAS SATISFACTORY.  THE LINKAGE WAS GOOD AND THE CARBURETOR O.K.  THERE WAS NO EXPLANATION OF WHY THE CARBURETOR BOLT WAS MISSING.  AIRCRAFT HAD FLOWN 70.6 HOURS SINCE THE LAST ANNUAL.  EXAMINATION OF LOGBOOKS REVEAL NO CARBURETOR OR CARBURETOR LINKAGE MAINTENANCE.

## The NTSB's investigation of this event (1)

From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model.

- [NTSB NYC00LA234](https://openairdocs.org/ntsb/NYC00LA234), Aug 19, 2000: Cessna 152 (N67495), Culpeper, VA, substantial damage. Probable cause: The partial loss of power due to an inadequate annual inspection, which resulted in the throttle linkage becoming disconnected from the throttle.

From the FAA Accident/Incident Data System. Reports are matched to registry aircraft by N-number and event date, checked against the reported make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. For accidents, the NTSB's own investigation is the fuller record.

---
OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.