# Incident 20031107031589I: Cessna 172P, Orlando, FL, November 7, 2003

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: November 7, 2003, 12:45 local time
- Place: Orlando, FL
- Airport: Orlando Sanford Airport
- Phase of flight: Ground Taxi, Other Airplane
- Operating rules: General operating rules (Part 91)
- Operator: CE8S
- Location: 28.7772° N, 81.2349° W: Placed by OpenAirDocs at ORLANDO SANFORD INTL (SFB), within about a mile (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=28.7772&lon=-81.2349&mi=10
- Aircraft: N52841, registered now (https://openairdocs.org/aircraft/N52841) (OpenAirDocs)
- Registry model: Cessna 172P (registry code 2072436, https://openairdocs.org/model/cessna-172p) (OpenAirDocs)
- Registry engine: Lycoming 0-320 series (registry code 41508, https://openairdocs.org/engine/lycoming-0-320-series) (OpenAirDocs)
- Reported make and model: CESSNA 172P
- People aboard: 2
- Fatal injuries: 0
- Pilot flight hours: 800 total, 500 in this make and model, 140 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20031107031589I

## Narrative

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

(-23) PILOT STATED, DURING TAXI AFTER LANDING AT SANFORD AIRPORT, HE TURNED THE LANDING LIGHT SWITCH OFF. SMOKING CAME FROM THE SWITCH AREA. HE ELECTED TO NOTIFY GROUND CONTROL HE HAD SMOKE IN THE COCKPIT. HE AND THE STUDENT SHUT DOWN THE ENGINE AND DEPARTED THE AIRCRAFT. MAINTENANCE TOWED THE AIRCRAFT TO THE HANGAR, TROUBLESHOT THE SYSTEM AND REPLACED THE SWITCH.

## Other reports on N52841 (1)

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

- [Incident 20190407002599I](https://openairdocs.org/incident/20190407002599I), Apr 7, 2019: Cessna 172P (N52841), Sanford, FL, No damage. A Cessna 172 operated by L3 in Sanford reported a bird strike while performing touch and go landings in order to resume with his initial solo flights. 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.