# Incident 20040117010689I: Boeing 7272J0, Kinston, NC, January 17, 2004

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: January 17, 2004, 01:13 local time
- Place: Kinston, NC
- Airport: Eastern Regional Jetport At Stall
- Phase of flight: Normal Cruise
- Operating rules: Air carrier (Part 121)
- Operator: RIVA
- Location: 35.2751° N, 77.5934° W: Placed by OpenAirDocs: center of Kinston, NC, within about 6 miles (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=35.2751&lon=-77.5934&mi=10
- Aircraft: N364PA, a cancelled registration (https://openairdocs.org/deregistered/N364PA-2006-06-13) (OpenAirDocs)
- Registry model: Boeing 727-2J0 (registry code 1384045, https://openairdocs.org/model/boeing-727-2j0) (OpenAirDocs)
- Registry engine: Pratt & Whitney JT8D-15 (registry code 52051, https://openairdocs.org/engine/pratt-whitney-jt8d-15) (OpenAirDocs)
- Reported make and model: BOEING 7272J0
- People aboard: 157
- Fatal injuries: 0
- Pilot flight hours: 15,000 total, 260 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20040117010689I

## Narrative

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

(-23) ON JANUARY 17, 2004 ON A ROUTINE FLIGHT FROM BOS TO CANCUN MEX AT 31000, FLIGHT 8510 WITH 149 PASSENGERS AND 8 CREW MEMBERS HAD A FORWARD CARGO COMPARTMENT FIRE WARNING LIGHT COME ON. THE FLIGHT CREW FOLLOWED THE EMERGENCY CHECKLIST PROCEDURES. ATC WAS ADVISED OF THE EMERGENCY AND SQUAKE 7700 CODE. AN EMERGENCY DESCENT TO THE NEAREST SUITABLE AIRPORT (KINSTON, NC ISO) WAS MADE. THE AIRCRAFT LANDED WITHOUT INCIDENT. ALL THE PASSENGERS WERE DEPLANED AND ALL BAGGAGE REMOVED FROM THE AIRCRAFT. FIRE CREWS PERSONNEL AND THE ONBOARD MECHANIC INSPECTED THE CARGO BINS. NO SMOKE OR FIRE DAMAGE WAS FOUND. THE PILOT, FIRST OFFICER, CHIEF INSPECTOR, DIRECTOR OF OPERATIONS AND PMI FOR PAN AM WERE CONTACTED. THE CHIEF INSPECTOR FOR PAN AM INFORMED ME THAT TWO SMOKE/FIRE DETECTORS HAD FAILED. DUE TO THE DUEL DETECTOR FAILURE THE FIRE WARNING LIGHT CAME ON. DOCUMENTATION WAS RECEIVED FROM PAN AM STATING THAT ONCE THE ROOT CAUSE OF THE DETECTOR FAILURES WERE ESTABLISHED THE INSTRUCTIONS FOR CONTINUED AIRWORTHINESS/INSPECTION PROGRAM WOULD BE REVISED TO ASSURE THIS TYPE OF FAILURE DID NOT REOCCUR AGAIN. THE PMI AND PAI FOR PAN AM WERE INFORMED FOR FOLLOW UP.

## Other reports on N364PA (5)

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

- [Incident 20010320004809I](https://openairdocs.org/incident/20010320004809I), Mar 20, 2001: Boeing 7272J0 (N364PA), Belleville, IL, Minor damage. (-23) Upon departure from blv, during landing gear retraction, the crew heard a loud clunk and the nose gear would not fully retract. The gear was extended and…
- [Incident 20001122021539I](https://openairdocs.org/incident/20001122021539I), Nov 22, 2000: Boeing 7272J0 (N364PA), Pittsburgh, PA, Minor damage. (-23) On November 22, 2000, a B-727, s/n 21107, registered as N364PA, and operated as "riva" flight #63, landed at "pit" after reporting an anti-skid problem…
- [Accident 20000728008539A](https://openairdocs.org/incident/20000728008539A), Jul 28, 2000: Boeing 7272J0 (N364PA), Charleston, SC, No damage. (-23) Pan am flight 164 departed sanford (sfr), FL, at 2053Z destined for pittsburg (pit), PA. While maneuvering between cells 60 miles south fo the cae…
- [Incident 20000502019559I](https://openairdocs.org/incident/20000502019559I), May 2, 2000: Boeing 7272J0 (N364PA), Pittsburgh, PA. (-23)While enroute from portsmouth, ma to Pittsburgh, PA over albany, PA, the #3 starter valve light illuminated. The power reduced and the light went out.…
- [Incident 19870608046289I](https://openairdocs.org/incident/19870608046289I), Jun 8, 1987: Boeing 727221 (N364PA), New York, NY. The NR1 leading edge flap failed to extend properly. A safe landing was made. Flap actuator was 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.