# Accident 19930603034309A: Piper J3C65, Greensboro, NC, June 3, 1993

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: June 3, 1993, 19:20 local time
- Place: Greensboro, NC
- Damage: Substantial damage
- Phase of flight: Fcd/Prec Ldg From Cruise
- Operating rules: General operating rules (Part 91)
- Location: 36.0006° N, 79.7598° W: From the FAA, an estimate near the named town, within about 3 miles
- Nearby events: https://openairdocs.org/map.md?lat=36.0006&lon=-79.7598&mi=10
- Aircraft: N87811, registered now (https://openairdocs.org/aircraft/N87811) (OpenAirDocs)
- Registry model: Piper J3C-65 (registry code 7100510, https://openairdocs.org/model/piper-j3c-65) (OpenAirDocs)
- Registry engine: Continental A&C65 series (registry code 17003, https://openairdocs.org/engine/continental-a-c65-series) (OpenAirDocs)
- Reported make and model: PIPER J3C65
- Reported engine: CONT A658
- People aboard: 1
- Fatal injuries: 0
- Pilot flight hours: 1,500 total, 600 in this make and model
- NTSB investigation: [NTSB ATL93LA102](https://openairdocs.org/ntsb/ATL93LA102) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/19930603034309A

## Narrative

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

LOST POWER EN ROUTE. STRUCK AND LODGED IN A TREE TOP ON FORCED LANDING. ENGINE TESTED NORMAL. CARB ICING EXISTED.

## 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 ATL93LA102](https://openairdocs.org/ntsb/ATL93LA102), Jun 3, 1993: Piper J3C-65 (N87811), Greensboro, NC, substantial damage. Probable cause: THE PILOT'S IMPROPER USE OF CARBURETOR HEAT DURING THE FLIGHT. FACTORS WERE THE CARBURETOR ICING CONDITIONS AT THE TIME OF THE ACCIDENT, AND TREES AT THE FORCED LANDING SITE

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.