# Incident 20030717031809I: Cessna 172RG, Reading, PA, July 17, 2003

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: July 17, 2003, 17:03 local time
- Place: Reading, PA
- Airport: Reading Municipal Gen Carl A Spaatz
- Damage: Minor damage
- Phase of flight: Final Approach
- Operating rules: General operating rules (Part 91)
- Location: 40.3392° N, 75.9263° W: Placed by OpenAirDocs: center of Reading, PA, within about 6 miles (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=40.3392&lon=-75.9263&mi=10
- Aircraft: N6419V, registered now (https://openairdocs.org/aircraft/N6419V) (OpenAirDocs)
- Registry model: Cessna 172RG (registry code 2072438, https://openairdocs.org/model/cessna-172rg) (OpenAirDocs)
- Registry engine: Lycoming O&VO-360 series (registry code 41514, https://openairdocs.org/engine/lycoming-o-vo-360-series) (OpenAirDocs)
- Reported make and model: CESSNA 172RG
- Pilot flight hours: 2,020 total, 350 in this make and model
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20030717031809I

## Narrative

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

(-23) LOCAL TOWER CONTROLLER, ^PRIVACY DATA^ HEARD "MASTER OFF" ON ONE OF HIS FREQUENCIES. NOT KNOWING WHO MADE THE TRANSMISSION, ^PRIVACY ^ STARTED LOOKING FOR ANYONE IN TROUBLE. HE ALERTLY OBSERVED N6419V, A CESSNA 172, ON LEFT DOWNWIND, ABRUPTLY TURN TOWARD N733MU ON FINAL TO RUNWAY 31. NOT KNOWING THE DEGREE OF DIFFICULTIES BEING EXPERIENCED BY N6419V, ^PRIVACY ^ SENT N733MU AROUND. THIS ALLOWED A STERILE RUNWAY FOR N6419V. AFTER LANDING, N6419V TURNED RIGHT AT TAXIWAY F AND ITS OCCUPANTS IMMEDIATELY EXITED THE AIRCRAFT AND EXTINGUISHED A FIRE IN THE COCKPIT. FIRE DAMAGE WAS VERY MINIMAL TO THE CARPETING. DURING INVESTIGATION, IT APPEARED THAT WIRING HAD CHAFED INTO A LANDING GEAR HYDRAULIC LINE AND CAUSED SMOKE AND HEAT, WHICH MAY HAVE IGNITED THE HYDRAULIC FLUID AND MELTED A PITOT/STATIC LINE. THIS IN TURN DRIPPED ONTO THE CARPET IN THE AREA OF THE RUDDER PEDALS. THE PIC USED THE CABIN FIRE EXTINGUISHER TO EXTINGUISH THE FLAMES, WITH MINIMAL DAMAGE TO THE AIRCRAFT.

## Other reports on N6419V (3)

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

- [Incident 20221112013769I](https://openairdocs.org/incident/20221112013769I), Nov 12, 2022: Cessna 172RG (N6419V), Frederick, MD, Minor damage. On approach to runway 23 at the Frederick Municipal Airport (fdk), MD, the pilot in command didn't extend the landing gear, resulting in a gear-up landing.…
- [Incident 20130706011149I](https://openairdocs.org/incident/20130706011149I), Jul 6, 2013: Cessna 172RG (N6419V), Frederick, MD, Minor damage. During training flight at fdk, the nose gear collapsed after landing, on roll out. The main gear remained down and locked.
- [Accident 19930813029521A](https://openairdocs.org/incident/19930813029521A), Aug 13, 1993: Cessna 172RG (N6419V), Philadelphia, PA, Substantial damage. Taxiing on ramp for takeoff. Left wing collided with parked N131CD that was preparing to leave parking area.

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.