37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 429038 |
Time | |
Date | 199902 |
Day | Thu |
Local Time Of Day | 1801 To 2400 |
Place | |
Locale Reference | atc facility : lga.tower airport : lga.airport |
State Reference | NY |
Altitude | msl single value : 1600 |
Environment | |
Flight Conditions | VMC |
Aircraft 1 | |
Controlling Facilities | tracon : n90.tracon tower : lga.tower |
Operator | common carrier : air carrier |
Make Model Name | Commercial Fixed Wing |
Operating Under FAR Part | Part 121 |
Navigation In Use | ils localizer only : 31 |
Flight Phase | descent : approach landing : go around |
Route In Use | approach : instrument non precision |
Flight Plan | IFR |
Aircraft 2 | |
Controlling Facilities | tower : lga.tower |
Operator | common carrier : air carrier |
Make Model Name | DC-9 Undifferentiated or Other Model |
Operating Under FAR Part | Part 121 |
Flight Phase | descent : approach |
Route In Use | approach : instrument non precision |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Qualification | pilot : multi engine pilot : commercial pilot : instrument |
Experience | flight time last 90 days : 100 flight time total : 8000 |
ASRS Report | 429038 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp |
Events | |
Anomaly | conflict : airborne less severe non adherence : published procedure non adherence : clearance other anomaly other |
Independent Detector | aircraft equipment : tcas other controllera |
Resolutory Action | controller : issued new clearance flight crew : executed go around |
Consequence | faa : reviewed incident with flight crew |
Miss Distance | horizontal : 15000 |
Supplementary | |
Problem Areas | ATC Human Performance |
Primary Problem | ATC Human Performance |
Air Traffic Incident | other |
Narrative:
Approach control vectored us on a base leg at 180 KIAS approximately 2 1/2 mi behind a DC9 for the localizer runway 31 at lga. We were then given a vector to intercept the final, cleared the localizer runway 31, and told to contact tower. Upon checking in with tower, we were asked if we had the DC9 in front of us in sight. Though we had the aircraft on the TCASII, we had lost visual contact with the DC9, as he blended in with the ground lights. We notified tower we did not have a visual with the DC9. Tower directed us to go around. We initiated the go around and climbed to 2000 ft MSL as directed by tower and switched to approach control. Due to the short climb from 1600 ft to 2000 ft with the change in the gear and flap confign and a frequency change, the frequency change to approach was delayed. In fact, after realizing I entered the frequency change incorrectly, I had to return to tower to confirm the proper frequency. Due to radio saturation, I was unacceptably delayed in reacquiring the frequency. In the meantime, the captain was executing the published missed approach which required a climbing right turn to the orchy NDB. When I finally got hold of approach control, they wanted to know why we were turning to orchy. I told the controller we were cleared the localizer 31 and when told to go around, executed the missed approach procedure. The controller wanted to know what instructions tower had given us on the go around. Both the captain and I heard 'go around, climb to 2000 ft, contact approach control.' never did we hear (or recall hearing) 'maintain runway heading.' due to the delay in contacting approach control, we flew the published missed approach. (He actually expected us to fly runway heading.) the situation could have been avoided if approach control hadn't originally put us in so tight on the DC9 (2 1/2 mi). Obviously, the unanticipated go around command, task saturation associated with the go around with only a short climb of 400 ft, and a frequency change led to the delay in contacting approach. This is a situation that could be repeated again in the future. I think the best way to reduce that likelihood is to quit trying to cram too many airplanes into confined airspace. More spacing would have prevented the go around in the first place.
Original NASA ASRS Text
Title: ACR FLC INSTRUCTED TO EXECUTE A MISSED APCH WHEN ADVISING ATC THEY COULD NOT SIGHT DC9 AHEAD ON FINAL. THE FLC EXECUTE A FULL MISSED APCH WHEN UNABLE TO CLARIFY FREQ, AND ARE QUESTIONED BY DEP CTL WHY THEY WERE NOT ON RWY HDG. FO CONCERNED WITH TFC SPACING AND FREQ CONGESTION WHICH DELAYED HIS FLT.
Narrative: APCH CTL VECTORED US ON A BASE LEG AT 180 KIAS APPROX 2 1/2 MI BEHIND A DC9 FOR THE LOC RWY 31 AT LGA. WE WERE THEN GIVEN A VECTOR TO INTERCEPT THE FINAL, CLRED THE LOC RWY 31, AND TOLD TO CONTACT TWR. UPON CHKING IN WITH TWR, WE WERE ASKED IF WE HAD THE DC9 IN FRONT OF US IN SIGHT. THOUGH WE HAD THE ACFT ON THE TCASII, WE HAD LOST VISUAL CONTACT WITH THE DC9, AS HE BLENDED IN WITH THE GND LIGHTS. WE NOTIFIED TWR WE DID NOT HAVE A VISUAL WITH THE DC9. TWR DIRECTED US TO GO AROUND. WE INITIATED THE GAR AND CLBED TO 2000 FT MSL AS DIRECTED BY TWR AND SWITCHED TO APCH CTL. DUE TO THE SHORT CLB FROM 1600 FT TO 2000 FT WITH THE CHANGE IN THE GEAR AND FLAP CONFIGN AND A FREQ CHANGE, THE FREQ CHANGE TO APCH WAS DELAYED. IN FACT, AFTER REALIZING I ENTERED THE FREQ CHANGE INCORRECTLY, I HAD TO RETURN TO TWR TO CONFIRM THE PROPER FREQ. DUE TO RADIO SATURATION, I WAS UNACCEPTABLY DELAYED IN REACQUIRING THE FREQ. IN THE MEANTIME, THE CAPT WAS EXECUTING THE PUBLISHED MISSED APCH WHICH REQUIRED A CLBING R TURN TO THE ORCHY NDB. WHEN I FINALLY GOT HOLD OF APCH CTL, THEY WANTED TO KNOW WHY WE WERE TURNING TO ORCHY. I TOLD THE CTLR WE WERE CLRED THE LOC 31 AND WHEN TOLD TO GO AROUND, EXECUTED THE MISSED APCH PROC. THE CTLR WANTED TO KNOW WHAT INSTRUCTIONS TWR HAD GIVEN US ON THE GAR. BOTH THE CAPT AND I HEARD 'GO AROUND, CLB TO 2000 FT, CONTACT APCH CTL.' NEVER DID WE HEAR (OR RECALL HEARING) 'MAINTAIN RWY HDG.' DUE TO THE DELAY IN CONTACTING APCH CTL, WE FLEW THE PUBLISHED MISSED APCH. (HE ACTUALLY EXPECTED US TO FLY RWY HDG.) THE SIT COULD HAVE BEEN AVOIDED IF APCH CTL HADN'T ORIGINALLY PUT US IN SO TIGHT ON THE DC9 (2 1/2 MI). OBVIOUSLY, THE UNANTICIPATED GAR COMMAND, TASK SATURATION ASSOCIATED WITH THE GAR WITH ONLY A SHORT CLB OF 400 FT, AND A FREQ CHANGE LED TO THE DELAY IN CONTACTING APCH. THIS IS A SIT THAT COULD BE REPEATED AGAIN IN THE FUTURE. I THINK THE BEST WAY TO REDUCE THAT LIKELIHOOD IS TO QUIT TRYING TO CRAM TOO MANY AIRPLANES INTO CONFINED AIRSPACE. MORE SPACING WOULD HAVE PREVENTED THE GAR IN THE FIRST PLACE.
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.