37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 605312 |
Time | |
Date | 200401 |
Day | Wed |
Local Time Of Day | 0601 To 1200 |
Place | |
Locale Reference | airport : boi.airport |
State Reference | ID |
Altitude | agl single value : 1500 |
Environment | |
Flight Conditions | Marginal |
Aircraft 1 | |
Controlling Facilities | tower : boi.tower |
Operator | common carrier : air carrier |
Make Model Name | B737-300 |
Operating Under FAR Part | Part 121 |
Navigation In Use | ils localizer & glide slope : 10r |
Flight Phase | descent : approach |
Route In Use | approach : visual |
Flight Plan | IFR |
Aircraft 2 | |
Controlling Facilities | tower : boi.tower |
Operator | common carrier : air carrier |
Make Model Name | Commercial Fixed Wing |
Operating Under FAR Part | Part 121 |
Flight Phase | ground : taxi |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp |
Experience | flight time last 90 days : 200 flight time total : 10200 |
ASRS Report | 605312 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Qualification | pilot : multi engine pilot : instrument pilot : commercial |
Experience | flight time last 90 days : 150 flight time total : 6500 flight time type : 3000 |
ASRS Report | 605313 |
Events | |
Anomaly | conflict : ground less severe non adherence : clearance other anomaly other other spatial deviation |
Independent Detector | other flight crewa |
Resolutory Action | controller : issued new clearance flight crew : executed go around other |
Consequence | faa : reviewed incident with flight crew |
Supplementary | |
Problem Areas | ATC Human Performance Weather Environmental Factor Flight Crew Human Performance |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation Inter Facility Coordination Failure |
Narrative:
With first officer flying, we established a downwind to boi runway 10R. Abeam the airport, I inquired with approach if other aircraft were doing visuals or staying ILS. I could see airport from our current position and thought we could execute a visual from that point. Approach responded 'yes' and asked if we had airport in sight.' I said 'yes.' he cleared us for 'visual to runway 10R.' the first officer turned inbound and wasn't sure if she had airport in sight. I gave initial headings to it as I did see the airport. I then called the tower and they cleared us to land runway 10L. Right after that, the first officer said she did not see airport, and asked me to take aircraft, which I did. I flew it to runway 10R and, at about 300 ft, noticed another aircraft take the runway. I executed a go around. We inquired why aircraft was on runway 10R and tower replied we were cleared for landing runway 10L. We finished the go around and came back to land on runway 10R using the ILS under visual conditions. I believe factors were confusing clrncs at same time of changing control of aircraft combined with some level of pilot fatigue as this was our 4TH leg of a long day. The landing clearance came right as I was concerned that first officer could see runway. I accepted it and immediately became PF. First officer did not hear the landing clearance as she was trying to see airport. Supplemental information from acn 605313: I felt the confusion was caused partly by the clearance from an ILS to a visual and no clear verbiage about a runway change (ie, now cleared).
Original NASA ASRS Text
Title: B737-300 FLT CREW PERFORMS A GAR AFTER SEEING ANOTHER ACFT XING THEIR ASSIGNED RWY 10R AT BOI, ID.
Narrative: WITH FO FLYING, WE ESTABLISHED A DOWNWIND TO BOI RWY 10R. ABEAM THE ARPT, I INQUIRED WITH APCH IF OTHER ACFT WERE DOING VISUALS OR STAYING ILS. I COULD SEE ARPT FROM OUR CURRENT POS AND THOUGHT WE COULD EXECUTE A VISUAL FROM THAT POINT. APCH RESPONDED 'YES' AND ASKED IF WE HAD ARPT IN SIGHT.' I SAID 'YES.' HE CLRED US FOR 'VISUAL TO RWY 10R.' THE FO TURNED INBOUND AND WASN'T SURE IF SHE HAD ARPT IN SIGHT. I GAVE INITIAL HDGS TO IT AS I DID SEE THE ARPT. I THEN CALLED THE TWR AND THEY CLRED US TO LAND RWY 10L. RIGHT AFTER THAT, THE FO SAID SHE DID NOT SEE ARPT, AND ASKED ME TO TAKE ACFT, WHICH I DID. I FLEW IT TO RWY 10R AND, AT ABOUT 300 FT, NOTICED ANOTHER ACFT TAKE THE RWY. I EXECUTED A GAR. WE INQUIRED WHY ACFT WAS ON RWY 10R AND TWR REPLIED WE WERE CLRED FOR LNDG RWY 10L. WE FINISHED THE GAR AND CAME BACK TO LAND ON RWY 10R USING THE ILS UNDER VISUAL CONDITIONS. I BELIEVE FACTORS WERE CONFUSING CLRNCS AT SAME TIME OF CHANGING CTL OF ACFT COMBINED WITH SOME LEVEL OF PLT FATIGUE AS THIS WAS OUR 4TH LEG OF A LONG DAY. THE LNDG CLRNC CAME RIGHT AS I WAS CONCERNED THAT FO COULD SEE RWY. I ACCEPTED IT AND IMMEDIATELY BECAME PF. FO DID NOT HEAR THE LNDG CLRNC AS SHE WAS TRYING TO SEE ARPT. SUPPLEMENTAL INFO FROM ACN 605313: I FELT THE CONFUSION WAS CAUSED PARTLY BY THE CLRNC FROM AN ILS TO A VISUAL AND NO CLR VERBIAGE ABOUT A RWY CHANGE (IE, NOW CLRED).
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.