# Incident 20040503020709I: Emb EMB135LR, Richmond, VA, May 3, 2004

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: May 3, 2004, 12:30 local time
- Place: Richmond, VA
- Airport: Richmond International - Byrd Field
- Phase of flight: Idling Engines
- Operating rules: Air carrier (Part 121)
- Operator: SIMA
- Location: 37.5538° N, 77.4603° W: Placed by OpenAirDocs: center of Richmond, VA, within about 6 miles (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=37.5538&lon=-77.4603&mi=10
- Aircraft: N734EK, a cancelled registration (https://openairdocs.org/deregistered/N734EK-2019-09-09) (OpenAirDocs)
- Registry model: Embraer EMB-135LR (registry code 3260305, https://openairdocs.org/model/embraer-emb-135lr) (OpenAirDocs)
- Registry engine: Allison AE3007C series (registry code 03028, https://openairdocs.org/engine/allison-ae3007c-series) (OpenAirDocs)
- Reported make and model: EMB EMB135LR
- People aboard: 35
- Fatal injuries: 0
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20040503020709I

## Narrative

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

(-23) JUST AFTER PARKING AT THE GATE, AND AFTER HAVING RESET THE APU GENERATOR TO "ON", A LARGE AMOUNT OF SMOKE WAS SEEN EMANATING FROM THE TAIL OF THE AIRCRAFT. THE CAPTAIN SHUT DOWN THE REMAINING ENGINE, #2, AND THE APU, AND DISCHARGED THE APU FIRE BOTTLE. THE PASSENGERS AND THE CREW DEPLANED UNEVENTFULLY INTO THE JETWAY, VIA THE MAIN CABIN DOOR, WITH NO INJURIES. THE CRASH AND RESCUE PERSONNEL RESPONDED, BUT WERE UNABLE TO FIND ANY EVIDENCE OF FIRE. COMPANY MAINTENANCE FOUND EVIDENCE OF A POSSIBLE APU INLET FIRE, AND THE AIRCRAFT WAS FERRIED TO A MAINTENANCE BASE, WHERE THE APU, APU INLET, APU GENERATOR AND APU FADEC CONTROL WERE REPLACED.

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.