# Incident 20060106002029I: Piper PA32R300, Raleigh, NC, January 6, 2006

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: January 6, 2006, 14:00 local time
- Place: Raleigh, NC
- Phase of flight: Normal Cruise
- Operating rules: General operating rules (Part 91)
- Operator: FFKA
- Location: 35.7721° N, 78.6386° W: Placed by OpenAirDocs: center of Raleigh, NC, within about 7 miles (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=35.7721&lon=-78.6386&mi=10
- Aircraft: N333TG, a cancelled registration (https://openairdocs.org/deregistered/N333TG-2012-08-13) (OpenAirDocs)
- Registry model: Piper PA-32R-300 (registry code 7103213, https://openairdocs.org/model/piper-pa-32r-300) (OpenAirDocs)
- Registry engine: Lycoming TI0-540 series (registry code 41533, https://openairdocs.org/engine/lycoming-ti0-540-series) (OpenAirDocs)
- Reported make and model: PIPER PA32R300
- Reported engine: LYC IO540K1A5D
- People aboard: 1
- Fatal injuries: 0
- Pilot flight hours: 3,071 total, 8 in this make and model, 128 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20060106002029I

## Narrative

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

(-23) TAKEOFF FROM RDU WAS UNSUCCESSFUL AND A CRUISE ALTITUDE OF 3,000 FEET WAS ESTABLISHED. AFTER A CLEARANCE OF 4,000 WAS RECEIVED A CRUISE CLIMB WAS ESTABLISHED. PASSING THROUGH 3,200 FEET A "POP" WAS HEARD AND INSTRUMENTS WERE SCANNED. MANIFOLD PRESSURE WAS APPROXIMATELY 30 INCHES OF MERCURY, 2500 RPM, OIL TEMP AND PRESSURE WERE IN THE GREEN. NOTING A LOSS OF ALTITUDE A STABILIZED DESCENT RATE WAS ESTABLISHED AT AN AIRSPEED OF 92 KIAS AND AN EMERGENCY LANDING FIELD WAS SELECTED. WHILE DESCENDING TO THE LANDING SITE THE EMERGENCY FLOW WAS FOLLOWED WITH NO SUCCESS OF AN ENGINE RESTART. ONCE THE FIELD WAS ASSURED FLAPS AND GEAR WERE DEPLOYED AND THE EMERGENCY LANDING COMPLETED. WHEN THE AIRPLANE CAME TO A COMPLETE STOP THE ENGINE AND PROPELLER STOPPED WIND MILLING. THE PILOT SAFELY EGRESSED THE AIRCRAFT WITH NO INJURIES. UPON POST-FLIGHT INSPECTION A STEADY FLOW OF OIL WAS OBSERVED STREAMING FROM UNDER THE LEFT SIDE OF THE COWLING.

## Other reports on N333TG (3)

Matched to the same aircraft by N-number and date.

- [Incident 20070907020789I](https://openairdocs.org/incident/20070907020789I), Sep 7, 2007: Piper PA32R300 (N333TG), Sanford, NC, Minor damage. (-23) Instructor pilot was teaching a simulated engine out emergencies on landing and delayed the gears down step in the landing checklist. Pilot realized the…
- [Accident 20050531012149A](https://openairdocs.org/incident/20050531012149A), May 31, 2005: Piper PA32R300 (N333TG), Ft Myers, FL, Substantial damage. (-23) On may 31, 2005, at 1745 EDT, a Piper PA-32R-300, registered to bellefonte inc., operated by ram air freight inc. (cert #FFKA873D), part 135 on…
- [Incident 20031022026329I](https://openairdocs.org/incident/20031022026329I), Oct 22, 2003: Piper PA32R300 (N333TG), Rock Hill, SC, Minor damage. (-23) On climbout from rockhill SC airport (uza) pilot set climb power and entered left turn. Pilot heard several loud noises from nose of aircraft and saw the…

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.