37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 595648 |
Time | |
Date | 200310 |
Day | Sun |
Local Time Of Day | 0601 To 1200 |
Place | |
Locale Reference | navaid : iciz.ils |
State Reference | KY |
Altitude | msl single value : 2100 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tracon : cvg.tracon |
Operator | common carrier : air carrier |
Make Model Name | B757-200 |
Operating Under FAR Part | Part 121 |
Navigation In Use | ils localizer & glide slope : 18l other |
Flight Phase | descent : approach |
Route In Use | approach : visual arrival : on vectors |
Flight Plan | IFR |
Aircraft 2 | |
Controlling Facilities | tracon : cvg.tracon |
Operator | common carrier : air carrier |
Make Model Name | Regional Jet CL65, Undifferentiated or Other Model |
Operating Under FAR Part | Part 121 |
Flight Phase | descent : approach |
Route In Use | approach : visual |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : flight engineer pilot : commercial pilot : atp pilot : instrument pilot : multi engine |
Experience | flight time last 90 days : 100 flight time total : 12600 flight time type : 3200 |
ASRS Report | 595648 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Events | |
Anomaly | conflict : airborne less severe non adherence : clearance |
Independent Detector | other controllera other flight crewa other flight crewb |
Resolutory Action | controller : issued new clearance flight crew : executed go around flight crew : took evasive action |
Miss Distance | horizontal : 3000 vertical : 800 |
Supplementary | |
Problem Areas | ATC Human Performance Flight Crew Human Performance |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
This situation had its beginning on the downwind leg for an approach to cvg runway 18L. The WX was cavu and we were in contact with cincinnati approach control throughout. As we turned base leg (heading 270 degrees), we were given a descent to 4000 ft MSL). We appeared to be high and approach control gave us a speed of 180 KTS and look for 'canadair' traffic to the south. We sighted traffic on the final approach course to runway 18L at 11 O'clock low position. It appeared to be a crj, so I reported the 'traffic in sight.' we were then cleared for the visual approach to runway 18L following the canadair. Our sighted traffic seemed to be 'no factor' in our approach, so we wondered about the speed restr, but maintained our assigned speed in compliance with ATC. Due to the reduced speed, my first officer was having difficulty getting the aircraft down and I was quite focused on helping him configure the aircraft, so as to get on a stabilized approach by 1000 ft (AGL). A sequence of events happened in rapid succession (whose order I am not quite certain): approaching fraze intersection (on the ILS to runway 18L -- FAF/fap) we continued to the high and were configuring, but a crj appeared in my field of vision about 1/2-1 mi ahead in a left turn for runway 18L (as if turning final from a left base). We had not switched to tower frequency due to my preoccupation with these other events, but it was in my mind to do so and was pre-selected in the inactive frequency control head. Sometime during this course of events the approach controller called us to see if we were still on his frequency. Of course, we were and he called the traffic we observed and gave us a 090 degree heading and a climb to 2500 ft MSL. We were now inside fraze approaching the river with an altitude around 2100 ft MSL. (Fraze GS interception altitude is 2400 ft MSL.) we executed the go around and turned downwind, base leg and final approach and landing without further incident. At no time did we receive a TCASII alert (TA or RA). I suspect the tower controller had called us on a number of occasions, because in-trail separation had been reduced and the fact that we were still on approach control was a cause for concern, but, it does not mitigate the fact that the main contributor to this incident was (what I assume was the case) misident of the called traffic. Secondary was my distraction of trying to assist the first officer with configuring the aircraft, getting the aircraft down and completing the checklists. I was prioritizing in order: aviate, navigate and communicate. I might have some minor criticism of the manner in which approach control called out our traffic. Rather than use a clock position with the addition of high, low, level, climbing, descending, etc, he chose to give a cardinal course/heading. This in no way excuses me from my 'see and avoid' responsibility in visual conditions. Note: the approach controller seemed to be switching most aircraft ahead of us to tower frequency upon issuing clearance for the visual approach. I do not remember this to be the case with us, though there were numerous instances of blocked radio xmissions on this frequency. Another possibility is that I received the switch to tower, but did not due to task saturation at the time, but I do remember looking up the tower frequency and pre-selecting it in the inactive radio control panel selection window. I was conscious of the fact that we had not switched to tower when we arrived at fraze and was in the midst of flap selection for the first officer.
Original NASA ASRS Text
Title: B757 CREW HAVE DIFFICULTY SIGHTING TFC AND CONFIGURING FOR A STABILIZED APCH INTO CVG.
Narrative: THIS SIT HAD ITS BEGINNING ON THE DOWNWIND LEG FOR AN APCH TO CVG RWY 18L. THE WX WAS CAVU AND WE WERE IN CONTACT WITH CINCINNATI APCH CTL THROUGHOUT. AS WE TURNED BASE LEG (HEADING 270 DEGS), WE WERE GIVEN A DSCNT TO 4000 FT MSL). WE APPEARED TO BE HIGH AND APCH CTL GAVE US A SPD OF 180 KTS AND LOOK FOR 'CANADAIR' TFC TO THE S. WE SIGHTED TFC ON THE FINAL APCH COURSE TO RWY 18L AT 11 O'CLOCK LOW POS. IT APPEARED TO BE A CRJ, SO I RPTED THE 'TFC IN SIGHT.' WE WERE THEN CLRED FOR THE VISUAL APCH TO RWY 18L FOLLOWING THE CANADAIR. OUR SIGHTED TFC SEEMED TO BE 'NO FACTOR' IN OUR APCH, SO WE WONDERED ABOUT THE SPD RESTR, BUT MAINTAINED OUR ASSIGNED SPD IN COMPLIANCE WITH ATC. DUE TO THE REDUCED SPD, MY FO WAS HAVING DIFFICULTY GETTING THE ACFT DOWN AND I WAS QUITE FOCUSED ON HELPING HIM CONFIGURE THE ACFT, SO AS TO GET ON A STABILIZED APCH BY 1000 FT (AGL). A SEQUENCE OF EVENTS HAPPENED IN RAPID SUCCESSION (WHOSE ORDER I AM NOT QUITE CERTAIN): APCHING FRAZE INTXN (ON THE ILS TO RWY 18L -- FAF/FAP) WE CONTINUED TO THE HIGH AND WERE CONFIGURING, BUT A CRJ APPEARED IN MY FIELD OF VISION ABOUT 1/2-1 MI AHEAD IN A L TURN FOR RWY 18L (AS IF TURNING FINAL FROM A L BASE). WE HAD NOT SWITCHED TO TWR FREQ DUE TO MY PREOCCUPATION WITH THESE OTHER EVENTS, BUT IT WAS IN MY MIND TO DO SO AND WAS PRE-SELECTED IN THE INACTIVE FREQ CTL HEAD. SOMETIME DURING THIS COURSE OF EVENTS THE APCH CTLR CALLED US TO SEE IF WE WERE STILL ON HIS FREQ. OF COURSE, WE WERE AND HE CALLED THE TFC WE OBSERVED AND GAVE US A 090 DEG HDG AND A CLB TO 2500 FT MSL. WE WERE NOW INSIDE FRAZE APCHING THE RIVER WITH AN ALT AROUND 2100 FT MSL. (FRAZE GS INTERCEPTION ALT IS 2400 FT MSL.) WE EXECUTED THE GAR AND TURNED DOWNWIND, BASE LEG AND FINAL APCH AND LNDG WITHOUT FURTHER INCIDENT. AT NO TIME DID WE RECEIVE A TCASII ALERT (TA OR RA). I SUSPECT THE TWR CTLR HAD CALLED US ON A NUMBER OF OCCASIONS, BECAUSE IN-TRAIL SEPARATION HAD BEEN REDUCED AND THE FACT THAT WE WERE STILL ON APCH CTL WAS A CAUSE FOR CONCERN, BUT, IT DOES NOT MITIGATE THE FACT THAT THE MAIN CONTRIBUTOR TO THIS INCIDENT WAS (WHAT I ASSUME WAS THE CASE) MISIDENT OF THE CALLED TFC. SECONDARY WAS MY DISTR OF TRYING TO ASSIST THE FO WITH CONFIGURING THE ACFT, GETTING THE ACFT DOWN AND COMPLETING THE CHKLISTS. I WAS PRIORITIZING IN ORDER: AVIATE, NAVIGATE AND COMMUNICATE. I MIGHT HAVE SOME MINOR CRITICISM OF THE MANNER IN WHICH APCH CTL CALLED OUT OUR TFC. RATHER THAN USE A CLOCK POS WITH THE ADDITION OF HIGH, LOW, LEVEL, CLBING, DSNDING, ETC, HE CHOSE TO GIVE A CARDINAL COURSE/HEADING. THIS IN NO WAY EXCUSES ME FROM MY 'SEE AND AVOID' RESPONSIBILITY IN VISUAL CONDITIONS. NOTE: THE APCH CTLR SEEMED TO BE SWITCHING MOST ACFT AHEAD OF US TO TWR FREQ UPON ISSUING CLRNC FOR THE VISUAL APCH. I DO NOT REMEMBER THIS TO BE THE CASE WITH US, THOUGH THERE WERE NUMEROUS INSTANCES OF BLOCKED RADIO XMISSIONS ON THIS FREQ. ANOTHER POSSIBILITY IS THAT I RECEIVED THE SWITCH TO TWR, BUT DID NOT DUE TO TASK SATURATION AT THE TIME, BUT I DO REMEMBER LOOKING UP THE TWR FREQ AND PRE-SELECTING IT IN THE INACTIVE RADIO CTL PANEL SELECTION WINDOW. I WAS CONSCIOUS OF THE FACT THAT WE HAD NOT SWITCHED TO TWR WHEN WE ARRIVED AT FRAZE AND WAS IN THE MIDST OF FLAP SELECTION FOR THE FO.
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.