ASN Wikibase Occurrence # 359949
This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information.
If you feel this information is incomplete or incorrect, you can
submit corrected information.
Date: | Friday 19 August 1994 |
Time: | 11:04 LT |
Type: | McDonnell Douglas MD-82 |
Owner/operator: | Alaska Airlines |
Registration: | N954AS |
MSN: | 49387/1288 |
Engine model: | P&W JT8D-217 |
Fatalities: | Fatalities: 0 / Occupants: 119 |
Aircraft damage: | None |
Category: | Serious incident |
Location: | Reno, NV -
United States of America
|
Phase: | En route |
Nature: | Unknown |
Departure airport: | (KRNO) |
Destination airport: | Seattle, WA (KSEA) |
Investigating agency: | NTSB |
Confidence Rating: | Accident investigation report completed and information captured |
Narrative:ALASKA AIRLINES FLIGHT 601 (ASA601), N954AS, WAS ON A STANDARD INSTRUMENT DEPARTURE WHEN IT NEARLY COLLIDED WITH A MOONEY M20C, N91Y. THE MOONEY WAS TRANSITING THE RENO AIRSPACE AT 12,500 FEET MSL AND HAD JUST BEEN HANDED OFF FROM THE TRACON DEPARTURE CONTROLLER TO THE ARRIVAL CONTROLLER. THE LOCAL CONTROLLER DID NOT INFORM ASA601 TO CONTACT DEPARTURE CONTROL AFTER TAKEOFF. DURING ASA601'S INITIAL CLIMB, THE DEPARTURE CONTROLLER/AREA MANAGER LEFT HIS POSITION TO ANSWER A PHONE CALL FROM A FACILITY TECHNICIAN TO DISCUSS TRACON BUSINESS. AT THE SAME TIME, THE ARRIVAL CONTROLLER WAS TELLING THE MOONEY TO CHANGE TRANSPONDER CODES IN PREPARATION FOR A HANDOFF TO CENTER; AT THAT TIME, THERE WAS SOME CONFUSION BETWEEN THE MOONEY PILOT AND THE CONTROLLER ABOUT THE TRANSPONDER CODE. THE ARRIVAL CONTROLLER SAID HE DID NOT SEE THE DATA BLOCK FOR ASA601 BECAUSE HIS ATTENTION WAS DIVERTED TO THE MOONEY. THE CHANGING OF THE TRANSPONDER CODE AND THE MOONEY'S INTERMITTENT MODE C TRANSPONDER KEPT ASA601'S TCAS SYSTEM FROM ACQUIRING THE MOONEY. AFTER HIS PHONE CALL, THE DEPARTURE CONTROLLER TRIED TO CALL ASA601, BUT WITHOUT SUCCESS. HE THEN CALLED THE LOCAL CONTROLLER AND WAS INFORMED OF THE NEAR COLLISION.
Probable Cause: FAILURE OF THE AREA SUPERVISOR/DEPARTURE CONTROLLER (SUPVR/CTLR) TO STAY AT HIS RADAR POSITION AND ENSURE THAT REQUIRED COMMUNICATIONS WERE MAINTAINED. FACTORS RELATED TO THE INCIDENT WERE: FAILURE OF THE LOCAL TOWER CONTROLLER INSTRUCT THE FLIGHTCREW OF ASA601 (N954AS) TO CONTACT DEPARTURE CONTROL, FAILURE OF THE ARRIVAL/DEPARTURE CONTROLLERS TO ISSUE TRAFFIC ADVISORIES, SUPERVISOR/DEPARTURE CONTROLLER'S DIVERTED ATTENTION, AND INTERMITTENT OPERATION OF THE TRANSPONDER IN THE MOONEY, THUS NOT ACTIVATING THE TCAS OF ASA601.
Accident investigation:
|
| |
Investigating agency: | NTSB |
Report number: | LAX94IA331 |
Status: | Investigation completed |
Duration: | 11 months |
Download report: | Final report |
|
Sources:
NTSB LAX94IA331
History of this aircraft
Other occurrences involving this aircraft
5 December 1996 |
N954AS |
Alaska Airlines |
0 |
Anchorage, AK |
|
min |
31 October 2010 |
ZS-TRE |
1Time |
0 |
Johannesburg-O.R. Tambo International Airport (JNB/FAJS) |
|
min |
Engine failure |
Location
Revision history:
Date/time | Contributor | Updates |
15-Mar-2024 16:20 |
ASN Update Bot |
Added |
The Aviation Safety Network is an exclusive service provided by:
CONNECT WITH US:
©2024 Flight Safety Foundation