19970418010839A

Accident

FAA accident report · Boeing 737-3S3 · Las Vegas, NV · April 18, 1997

Date
April 18, 1997 · 18:24 local
Place
Las Vegas, NV
Airport
Mc Carran International
Phase of flight
Normal Cruise
Operating rules
Air carrier (Part 121)
Operator
AWXA
Aircraft
N313AW
NTSB investigation
NTSBLAX97FA164
Reported as
Boeing 7373S3
Reported engine
CFMINT CFM563B2
People aboard
124
Fatal injuries
0
Pilot’s flight hours
14,500 total5,600 in this make and model227 in the last 90 days

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.

(.4)Beech 99 (B99) departed on VFR flight (flt) & began climb to 10,500', heading 175 deg. At boundary of class b airspace, ATC controller (TRACON) terminated radar service as B99 was at 7,000'; 40 sec later, pilots (plts) of Boeing 737 (B737) contacted TRACON, on cresso 3 arrival (star), & were cleared to descend to 10,000' on converging vector of 020 deg; 50 sec later, TRACON advised B737 of traffic (B99), 3 mi ahead, opposite direction & 1,700' lower. TRACON did not mention traffic was climbing, nor issue safety alert; 18 sec later, TRACON told B737 plts they could 'climb as you wish.' 1st officer (fo, plt flying TCAS equipped B737) responded to a resolution advisory by using autopilot & neglected to press 'level change,' which delayed avoidance maneuver. B737 plts saw B99 at close range; fo maneuvered abruptly to avert collision. B737 flight attendant was injured during maneuver. B99 plt saw B737 behind window post, too late for evasive action. Aircraft passed with estimated 200' vertical & no lateral separation (sepn). TCAS event analysis concluded that if B737 pilots had responded to TCAS advisories, within system design parameters, there would have been 700' vertical sepn w ithout abrupt maneuvering. Star was in heavily traveled area, often used by plts of small VFR aircraft.

As the FAA filed it

(.4)BEECH 99 (B99) DEPARTED ON VFR FLIGHT (FLT) & BEGAN CLIMB TO 10,500', HEADING 175 DEG. AT BOUNDARY OF CLASS B AIRSPACE, ATC CONTROLLER (TRACON) TERMINATED RADAR SERVICE AS B99 WAS AT 7,000'; 40 SEC LATER, PILOTS (PLTS) OF BOEING 737 (B737) CONTACTED TRACON, ON CRESSO 3 ARRIVAL (STAR), & WERE CLEARED TO DESCEND TO 10,000' ON CONVERGING VECTOR OF 020 DEG; 50 SEC LATER, TRACON ADVISED B737 OF TRAFFIC (B99), 3 MI AHEAD, OPPOSITE DIRECTION & 1,700' LOWER. TRACON DID NOT MENTION TRAFFIC WAS CLIMBING, NOR ISSUE SAFETY ALERT; 18 SEC LATER, TRACON TOLD B737 PLTS THEY COULD 'CLIMB AS YOU WISH.' 1ST OFFICER (FO, PLT FLYING TCAS EQUIPPED B737) RESPONDED TO A RESOLUTION ADVISORY BY USING AUTOPILOT & NEGLECTED TO PRESS 'LEVEL CHANGE,' WHICH DELAYED AVOIDANCE MANEUVER. B737 PLTS SAW B99 AT CLOSE RANGE; FO MANEUVERED ABRUPTLY TO AVERT COLLISION. B737 FLIGHT ATTENDANT WAS INJURED DURING MANEUVER. B99 PLT SAW B737 BEHIND WINDOW POST, TOO LATE FOR EVASIVE ACTION. AIRCRAFT PASSED WITH ESTIMATED 200' VERTICAL & NO LATERAL SEPARATION (SEPN). TCAS EVENT ANALYSIS CONCLUDED THAT IF B737 PILOTS HAD RESPONDED TO TCAS ADVISORIES, WITHIN SYSTEM DESIGN PARAMETERS, THERE WOULD HAVE BEEN 700' VERTICAL SEPN W ITHOUT ABRUPT MANEUVERING. STAR WAS IN HEAVILY TRAVELED AREA, OFTEN USED BY PLTS OF SMALL VFR AIRCRAFT.

NTSB investigation

The NTSB’s investigation of this event, with its probable cause and findings. Matched to this report by N-number and date.

Other reports on N313AW · 1

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