# Incident 20111108026889I: Piper PA-28-161, Fort Lauderdale, FL, November 8, 2011

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: November 8, 2011, 09:00 local time
- Place: Fort Lauderdale, FL
- Damage: No damage
- Phase of flight: Run-Up Area
- Operating rules: General operating rules (Part 91)
- Operator: TAGK
- Location: 26.1223° N, 80.1434° W: Placed by OpenAirDocs: center of Fort Lauderdale, FL, within about 6 miles (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=26.1223&lon=-80.1434&mi=10
- Aircraft: N83960, registered now (https://openairdocs.org/aircraft/N83960) (OpenAirDocs)
- Registry model: Piper PA-28-161 (registry code 7102803, https://openairdocs.org/model/piper-pa-28-161) (OpenAirDocs)
- Registry engine: Lycoming 0-320 series (registry code 41508, https://openairdocs.org/engine/lycoming-0-320-series) (OpenAirDocs)
- Reported make and model: PIPER PA-28-161
- Reported engine: LYCOMING 0-320 SERIES
- People aboard: 3
- Fatal injuries: 0
- Other injuries: 0
- Pilot certificates: Commercial pilot, flight instructor
- Pilot flight hours: 500 total, 15 in this make and model, 35 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20111108026889I

## Narrative

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

ON NOVEMBER 8, 2011, AIRCRAFT N83960, A PIPER PA-28-161, PILOTED BY ^PRIVACY DATA OMITTED^ WAS TAXING THE AIRCRAFT TO THE RUN-UP AREA AND PERFORMED AN ENGINE CHECK. DURING THE ENGINE CHECK THE PILOT SMELLED AND NOTICED SMOKE BEGAN ENTERING THE COCKPIT FROM THE ENGINE COMPARTMENT . THE PILOT NOTIFIED FXE ATC AND REPORTED THE INCIDENT AT WHICH TIME FXE ATC DECLARED AN EMERGENCY AND CLEARED ALL TRAFFIC AND DIRECTED THE PILOT TO TAXI TO AN OPEN RAMP. ATC DISPATCHED FIRE RESCUE TO THE RAMP AREA OF THE AIRCRAFT WHERE THE PILOT AND THE TWO PASSENGERS HAD EVACUATED THE AIRCRAFT. THERE WAS NOT ANY EVIDENCE OF FIRE JUST SMOKE. AFTERWARDS THE SMOKE CLEARED, THE PILOT CONTACTED A MECHANIC (^PRIVACY DATA OMITTED^)AND STATED THE PROBLEM AND HAD THE MECHANIC TO INSPECT THE AIRCRAFT. ^PRIVACY DATA OMITTED^ INSPECTED AND OPERATED THE AIRCRAFT AND COULD NOT RE-CREATE THE SMOKE CONDITION. ^PRIVACY DATA OMITTED^ ADVISED THE PILOT TO TAKE THE AIRCRAFT TO AN AVIONICS SHOP AND HAVE THEM CHECK THE AIRCRAFT. THIS WAS ACCOMPLISHED AND THE VHF NAV/COMM TRANSMITTER WAS FOUND TO BE BURNED OUT. THE UNIT WAS REPAIRED BY REPLACEMENT OF THE ENTIRE UNIT, A LOG BOOK ENTRY WAS MADE, RTS

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.