# Incident 19990609029939I: Fokker F28MK0100, Sioux Falls, SD, June 9, 1999

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: June 9, 1999, 20:35 local time
- Place: Sioux Falls, SD
- Airport: Joe Foss Field
- Phase of flight: Normal Cruise
- Operating rules: Air carrier (Part 121)
- Operator: AALA
- Location: 43.5820° N, 96.7419° W: Placed by OpenAirDocs at JOE FOSS FLD (FSD), within about a mile (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=43.5820&lon=-96.7419&mi=10
- Aircraft: N1460A, a cancelled registration (https://openairdocs.org/deregistered/N1460A-2004-05-26) (OpenAirDocs)
- Registry model: Fokker F.28 MK 0100 (registry code 4990807, https://openairdocs.org/model/fokker-f-28-mk-0100) (OpenAirDocs)
- Registry engine: Rolls-Royce TAY-650-15 (registry code 54557, https://openairdocs.org/engine/rolls-royce-tay-650-15) (OpenAirDocs)
- Reported make and model: FOKKER F28MK0100
- Pilot flight hours: 3,452 in this make and model
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/19990609029939I

## Narrative

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

(-23) WHILE N1460A WAS ENROUTE FROM MSP TO DFW, FLIGHT ATTENDANT ADVISED COCKPIT CREW THAT SOMETHING WAS BURNING IN THE GALLEY, SMOKE AND SOURCE COULD NOT BE IDENTIFIED. AN EMERGENCY WAS DECLARED AND AIRCRAFT DIVERTED TO FSD.  PRIOR TO LANDING, SMOKE DISSIPATED.  MECHANIC FOUND SOME CHARRED WIRES IN THE AREA OF OVEN CONTROLS.  INSPECTION CONFIRMED FORWARD OVEN FAN WIRES TO BE THE CAUSE OF THE SMOKE.

## Other reports on N1460A (1)

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

- [Incident 20020620036109I](https://openairdocs.org/incident/20020620036109I), Jun 20, 2002: Fokker F28MK0100 (N1460A), Memphis, TN. (-23) American airlines, flight #2069, registration N1460, F-28 Fokker, flight plan cvg-dfw, diverted into mem, declaring an emergency. The number one engine…

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.