# Incident 19980702027759I: Boeing 737201, Raleigh-Durham, NC, July 2, 1998

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: July 2, 1998, 20:20 local time
- Place: Raleigh-Durham, NC
- Airport: Raleigh-Durham International
- Damage: Minor damage
- Phase of flight: Normal Cruise
- Operating rules: Air carrier (Part 121)
- Operator: USAA
- Location: 35.8776° N, 78.7875° W: Placed by OpenAirDocs at RALEIGH-DURHAM INTL (RDU), within about a mile (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=35.8776&lon=-78.7875&mi=10
- Aircraft: N259AU, a cancelled registration (https://openairdocs.org/deregistered/N259AU-2003-11-04) (OpenAirDocs)
- Registry model: Boeing 737-201 (registry code 1384454, https://openairdocs.org/model/boeing-737-201) (OpenAirDocs)
- Registry engine: Pratt & Whitney JT8D-9 series (registry code 52048, https://openairdocs.org/engine/pratt-whitney-jt8d-9-series) (OpenAirDocs)
- Reported make and model: BOEING 737201
- Reported engine: PWA JT8D9
- People aboard: 2
- Fatal injuries: 0
- Pilot flight hours: 23,115 total, 7,047 in this make and model, 30 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/19980702027759I

## Narrative

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

FLIGHT ORIGINAL ROUTE WAS LGA TO JAX. AT FL350 DURING CRUISE THE FORWARD GALLEY OVEN CAUGHT FIRE. THE FLIGHT ATTENDANT USED A FIRE EXTINGUISHER TO PUT OUT FIRE. APPROXIMATELY 30 MINUTES LATER FIRE REOCCURRED & FLT ATTENDANT FROM REAR OF AIRCRAFT CAME TO HELP & INHALED SMOKE. FLT ATTENDANT THEN WENT INTO COCKPIT TO INFORM CAPTAIN FIRE HAD RESTARTED & SMOKE ENTERED COCKPIT. CREW WENT ON OXYGEN. CAPT DECLARED EMERGENCY WITH ATC & SENT F/O TO HELP PUT OUT FIRE. F/O USED HALON TO  EXTINGUISH FIRE. A/C DIVERTED TO RDU. PASSENGERS WERE EXITED THRU JETWAY WITH NO INJURIES. F/A WOLFE TAKE TO HOSPITAL FOR POSSIBLE SMOKE INHALATION. NO OTHER INJURIES. ALL INFO ON THIS INCIDENT SENT TO CMO BY USAIRWAYS.

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.