# Incident 20040921021719I: Cessna 172N, Hillsboro, OR, September 21, 2004

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: September 21, 2004, 15:05 local time
- Place: Hillsboro, OR
- Phase of flight: Normal Cruise
- Operating rules: General operating rules (Part 91)
- Location: 45.5253° N, 122.9364° W: Placed by OpenAirDocs: center of Hillsboro, OR, within about 6 miles (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=45.5253&lon=-122.9364&mi=10
- Aircraft: N733WX, registered now (https://openairdocs.org/aircraft/N733WX) (OpenAirDocs)
- Registry model: Cessna 172N (registry code 2072434, https://openairdocs.org/model/cessna-172n) (OpenAirDocs)
- Registry engine: Lycoming 0-320 series (registry code 41508, https://openairdocs.org/engine/lycoming-0-320-series) (OpenAirDocs)
- Reported make and model: CESSNA 172N
- People aboard: 2
- Fatal injuries: 0
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20040921021719I

## Narrative

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

(-23) AT APPROXIMATELY 2205Z ON 09/21/2004 WHILE OPERATING N733XW, A CESSNA 172N, CFI FRANK MARSHALL AND STUDENT PILOT PHILLIP GARNER NOTICED SMOKE AND FIRE IN THE COCKPIT. MR. MARSHALL NOTIFIED HIO ATC AND RECEIVED CLEARANCE FOR AN EMERGENCY LANDING. MR. MARSHALL LANDED WITHOUT INCIDENT. SUBSEQUENT INSPECTION DETERMINED THE LANDING LIGHT CIRCUIT HARNESS AND ASSOCIATED WIRES HAD CHAFFED ON AN AIRFRAME BULKHEAD CAUSING THE LANDING LIGHT SWITCH TO SHORT AND BURN.

## Other reports on N733WX (1)

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

- [Accident 19990905042689A](https://openairdocs.org/incident/19990905042689A), Sep 5, 1999: Cessna 172N (N733WX), Carlsbad, CA, Substantial damage. (.4)On September 5, 1999, about 1300 hours pacific daylight time, a Cessna 172N, N733WX, sustained substantial damage during taxi for takeoff at 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.