37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 458927 |
Time | |
Date | 199912 |
Day | Sat |
Local Time Of Day | 0601 To 1200 |
Place | |
Locale Reference | airport : lgb.airport |
State Reference | CA |
Altitude | msl bound lower : 11300 msl bound upper : 12000 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tracon : sct.tracon |
Operator | common carrier : air carrier |
Make Model Name | A320 |
Operating Under FAR Part | Part 121 |
Navigation In Use | other |
Flight Phase | descent : vacating altitude |
Route In Use | arrival : on vectors |
Flight Plan | IFR |
Aircraft 2 | |
Controlling Facilities | tracon : sct.tracon |
Operator | common carrier : air carrier |
Make Model Name | B737-300 |
Operating Under FAR Part | Part 121 |
Flight Phase | climbout : vacating altitude |
Route In Use | departure : on vectors |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp pilot : multi engine |
Experience | flight time last 90 days : 150 flight time total : 12500 flight time type : 2500 |
ASRS Report | 458927 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Qualification | pilot : multi engine pilot : commercial pilot : instrument |
Events | |
Anomaly | conflict : airborne critical non adherence : required legal separation non adherence : published procedure |
Independent Detector | atc equipment other atc equipment : radar aircraft equipment : tcas other controllera |
Resolutory Action | controller : issued advisory flight crew : took evasive action |
Consequence | other other Other |
Miss Distance | horizontal : 6000 vertical : 700 |
Supplementary | |
Problem Areas | Airspace Structure Flight Crew Human Performance ATC Human Performance |
Primary Problem | ATC Human Performance |
Air Traffic Incident | Operational Error |
Narrative:
During descent, the first officer was the PF. At about 12000 ft altitude, and 40-50 NM southeast of pounds (destination airport) while I was updating ATIS on communication #2, socal approach control reported an air carrier B737 at 1 O'clock, low, opposite direction. The first officer made visual contact at the 2 O'clock position, moving to 3 O'clock. I never had visual contact with the B737. As I returned to the socal frequency on communication #1, the TCASII gave an aural TA, and I noted an amber target displayed at our 4 O'clock position, less than 1 mi horizontal, 700 ft below. The TA was followed immediately by an RA 'climb, climb now!' I reacted by advancing the thrust levers to toga and applying full aft stick. Almost immediately, and before the aircraft climbed more than 100 ft, the RA was replaced by a 'clear of conflict' advisory. Total altitude gain was 150 ft. Time wise, the entire incident from TA until clear of conflict was probably 5-6 seconds. Socal was advised of the RA and actions taken. The controller replied that the aircraft in question was the B737 previously reported. The first officer reported later that the B737 appeared almost at our altitude as it closed, and its relative position visually did not correspond with the threat displayed by TCASII. Therefore, since he could not confirm positive visual contact with the threat, he also made an attempt to climb immediately. Descent to 8000 ft was resumed. Before passing 10000 ft, however, the first flight attendant came to the flight deck to report that the second flight attendant had been injured during the escape maneuver when he fell to the floor in the cabin aisleway. He complained of pain in one ankle. He was assisted to a passenger seat where he remained until the aircraft was parked. The second flight attendant was examined in the terminal by paramedics and taken to a hospital. Later, a nurse reported to me by telephone that further examination and x-ray revealed no breaks or fractures. The ankle was splinted and the flight attendant was released on crutches. After landing, I notified system operations control and discussed the incident with maintenance control and a representative of alpa. The first officer and I also proceeded to a local urgent care center for drug testing on the advice of the company chief pilot. It is my opinion that the aircraft system (TCASII and flight controls) worked as stated in the fcom, and no apparent malfunctions were noted. The aircraft was subsequently released by the NTSB and maintenance control for the return flight to phoenix.
Original NASA ASRS Text
Title: AN A320 PIC TAKES OVER FROM HIS FO AND PERFORMS A DRAMATIC EVASIVE ACTION CLB FOR OPPOSITE DIRECTION TFC WHEN TCASII RA ORDERS CLB COMMAND. A CABIN ATTENDANT IS INJURED FROM THE PULL UP.
Narrative: DURING DSCNT, THE FO WAS THE PF. AT ABOUT 12000 FT ALT, AND 40-50 NM SE OF LBS (DEST ARPT) WHILE I WAS UPDATING ATIS ON COM #2, SOCAL APCH CTL RPTED AN ACR B737 AT 1 O'CLOCK, LOW, OPPOSITE DIRECTION. THE FO MADE VISUAL CONTACT AT THE 2 O'CLOCK POS, MOVING TO 3 O'CLOCK. I NEVER HAD VISUAL CONTACT WITH THE B737. AS I RETURNED TO THE SOCAL FREQ ON COM #1, THE TCASII GAVE AN AURAL TA, AND I NOTED AN AMBER TARGET DISPLAYED AT OUR 4 O'CLOCK POS, LESS THAN 1 MI HORIZ, 700 FT BELOW. THE TA WAS FOLLOWED IMMEDIATELY BY AN RA 'CLB, CLB NOW!' I REACTED BY ADVANCING THE THRUST LEVERS TO TOGA AND APPLYING FULL AFT STICK. ALMOST IMMEDIATELY, AND BEFORE THE ACFT CLBED MORE THAN 100 FT, THE RA WAS REPLACED BY A 'CLR OF CONFLICT' ADVISORY. TOTAL ALT GAIN WAS 150 FT. TIME WISE, THE ENTIRE INCIDENT FROM TA UNTIL CLR OF CONFLICT WAS PROBABLY 5-6 SECONDS. SOCAL WAS ADVISED OF THE RA AND ACTIONS TAKEN. THE CTLR REPLIED THAT THE ACFT IN QUESTION WAS THE B737 PREVIOUSLY RPTED. THE FO RPTED LATER THAT THE B737 APPEARED ALMOST AT OUR ALT AS IT CLOSED, AND ITS RELATIVE POS VISUALLY DID NOT CORRESPOND WITH THE THREAT DISPLAYED BY TCASII. THEREFORE, SINCE HE COULD NOT CONFIRM POSITIVE VISUAL CONTACT WITH THE THREAT, HE ALSO MADE AN ATTEMPT TO CLB IMMEDIATELY. DSCNT TO 8000 FT WAS RESUMED. BEFORE PASSING 10000 FT, HOWEVER, THE FIRST FLT ATTENDANT CAME TO THE FLT DECK TO RPT THAT THE SECOND FLT ATTENDANT HAD BEEN INJURED DURING THE ESCAPE MANEUVER WHEN HE FELL TO THE FLOOR IN THE CABIN AISLEWAY. HE COMPLAINED OF PAIN IN ONE ANKLE. HE WAS ASSISTED TO A PAX SEAT WHERE HE REMAINED UNTIL THE ACFT WAS PARKED. THE SECOND FLT ATTENDANT WAS EXAMINED IN THE TERMINAL BY PARAMEDICS AND TAKEN TO A HOSPITAL. LATER, A NURSE RPTED TO ME BY TELEPHONE THAT FURTHER EXAMINATION AND X-RAY REVEALED NO BREAKS OR FRACTURES. THE ANKLE WAS SPLINTED AND THE FLT ATTENDANT WAS RELEASED ON CRUTCHES. AFTER LNDG, I NOTIFIED SYS OPS CTL AND DISCUSSED THE INCIDENT WITH MAINT CTL AND A REPRESENTATIVE OF ALPA. THE FO AND I ALSO PROCEEDED TO A LCL URGENT CARE CTR FOR DRUG TESTING ON THE ADVICE OF THE COMPANY CHIEF PLT. IT IS MY OPINION THAT THE ACFT SYS (TCASII AND FLT CTLS) WORKED AS STATED IN THE FCOM, AND NO APPARENT MALFUNCTIONS WERE NOTED. THE ACFT WAS SUBSEQUENTLY RELEASED BY THE NTSB AND MAINT CTL FOR THE RETURN FLT TO PHOENIX.
Data retrieved from NASA's ASRS site as of July 2007 and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.