OpenAirDocs.org

20000710025209I

Incident
Open the Markdown

FAA incident report · Boeing 737-2H4 · Amarillo, TX · July 10, 2000

FAA Aviation Safety Information Portal

© OpenStreetMap
Date
July 10, 2000 · 11:03 local
Place
Amarillo, TX
Phase of flight
Normal Cruise
Operating rules
Air carrier (Part 121)
Operator
SWAA
Aircraft
N62SW
Reported as
Boeing 7372H4
Pilot’s flight hours
7,500 total5,400 in this make and model232 in the last 90 days
N62SWRegistration cancelled Dec 9, 2002 · Boeing 737-2H4S/N 22060 · Built 1980Airframe modelBoeing 737-2H4Engine modelPratt & Whitney JT8D-9 seriesTurbo-jet

From the FAA’s Accident/Incident Data System (AIDS), through its Aviation Safety Information Portal, as reported. The NTSB investigates accidents separately, and its record of an accident is the fuller one. The aircraft is matched to the registry 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.

What happened

The FAA’s narrative, in sentence case. The FAA writes it in capitals and removes private details.

(-23)Plt. 2064 enroute tul-phx at optimum FL 310 with FL 350 available near abq. Aprox. 325 NM east of abq, ayc cleared to FL350. Upon reaching FL 330, climb diminished to 500FPM with as 250K. Slowed to 220K attempting to maintain climb. Aircraft leveled at FL 348 and continued to lose speed. Requested descent to FL 310, ATC advised unavailable. Aicraft began descent to maintain airspeed and declared emergency. Conflicting traffic was given descent and vectors to clear airspace for flt. 2064. Flt, assigned FL 310 and continued to phx. Onboard performance computer (opc) indicated FL 350 was available at their weight, however OAT was 20C warmer than anticipated at 350. OAT at FL310 was apparently not used to update opc thus giving invalid data for maximum available FL. Counseling and crew retraining has been accomplished. Chso looking into dispatch procedures and use of opc. A climb to 350 has initiated 325 NM prior in flight shown to be optimum altitude for cruise. Related report (ZAB-016)

As the FAA filed it

(-23)PLT. 2064 ENROUTE TUL-PHX AT OPTIMUM FL 310 WITH FL 350 AVAILABLE NEAR ABQ. APROX. 325 NM EAST OF ABQ, AYC CLEARED TO FL350. UPON REACHING FL 330, CLIMB DIMINISHED TO 500FPM WITH AS 250K. SLOWED TO 220K ATTEMPTING TO MAINTAIN CLIMB. AIRCRAFT LEVELED AT FL 348 AND CONTINUED TO LOSE SPEED. REQUESTED DESCENT TO FL 310, ATC ADVISED UNAVAILABLE. AICRAFT BEGAN DESCENT TO MAINTAIN AIRSPEED AND DECLARED EMERGENCY. CONFLICTING TRAFFIC WAS GIVEN DESCENT AND VECTORS TO CLEAR AIRSPACE FOR FLT. 2064. FLT, ASSIGNED FL 310 AND CONTINUED TO PHX. ONBOARD PERFORMANCE COMPUTER (OPC) INDICATED FL 350 WAS AVAILABLE AT THEIR WEIGHT, HOWEVER OAT WAS 20C WARMER THAN ANTICIPATED AT 350. OAT AT FL310 WAS APPARENTLY NOT USED TO UPDATE OPC THUS GIVING INVALID DATA FOR MAXIMUM AVAILABLE FL. COUNSELING AND CREW RETRAINING HAS BEEN ACCOMPLISHED. CHSO LOOKING INTO DISPATCH PROCEDURES AND USE OF OPC. A CLIMB TO 350 HAS INITIATED 325 NM PRIOR IN FLIGHT SHOWN TO BE OPTIMUM ALTITUDE FOR CRUISE. RELATED REPORT (ZAB-016)

Other reports on N62SW · 1

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

Incident 19990515015719IGround Taxi, Other Airplane · Albuquerque, NMOn may 15, 1999, at approximately 0700 am, swaa flight 1163 taxied for departure. A low pressure oil light illuminated and the aircraft returned to the gate. Maintenance inspected the aircraft and found a sensor was out. Parts were flown in from phx and…May 15, 1999