# Incident 20060306005689I: Piper PA32R300, Raleigh-Durham, NC, March 6, 2006

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: March 6, 2006, 10:00 local time
- Place: Raleigh-Durham, NC
- Airport: Raleigh-Durham International
- Damage: No damage
- Operating rules: General operating rules (Part 91)
- Location: 35.8776° N, 78.7875° W: Placed by OpenAirDocs at RALEIGH-DURHAM INTL (RDU), within about a mile (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=35.8776&lon=-78.7875&mi=10
- Aircraft: N220L, registered now (https://openairdocs.org/aircraft/N220L) (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
- Fatal injuries: 0
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20060306005689I

## Narrative

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

(-23) PILOT WAS ENROUTE TO KCSY. WHILE 45 NM NE OF RDU THE AIRCRAFT BEGAN ACCUMULATING ICE. THE PILOT ADVISED ATC AND REQUESTED A HIGHER ALTITUDE. ATC ASKED HIM TO STANDBY. THE AIRCRAFT CONTINUED TO ACCUMULATE ICE AND ANOTHER REQUEST WAS MADE FOR A HIGHER ALTITUDE. ATC ADVISED UNABLE AT THIS TIME AND GAVE THE PILOT A TURN. AS THE PILOT MADE HIS TURN, ICE CONTINUED TO ACCUMULATE AND THE PILOT INITIATED A CLIMB. WHEN QUERIED BY ATC, THE PILOT DECLARED AN EMERGENCY DUE TO ICE BUILD UP. ATC CLEARED HIM TO A HIGHER ALTITUDE AND CLEARED THE ICING AREA.

## Other reports on N220L (1)

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

- [Incident 19891006053049I](https://openairdocs.org/incident/19891006053049I), Oct 6, 1989: Piper PA32R300 (N220L), Block Island, RI, Minor damage. Pilot struck deer on landing rollout.

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.