 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
A B737-300 flight crew causes an F86 aircraft to go around when they taxi past the primary designated approach hold short line for runway 31 at bna, tn.
| Attributes | |
| ACN | 518165 |
| Time | |
| Date | 200107 |
| Day | Thu |
| Local Time Of Day | 0601 To 1200 |
| Place | |
| Locale Reference | airport : bna.airport |
| State Reference | TN |
| Altitude | agl single value : 0 |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Controlling Facilities | tower : bna.tower |
| Operator | common carrier : air carrier |
| Make Model Name | B737-300 |
| Operating Under FAR Part | Part 121 |
| Flight Phase | ground : taxi |
| Flight Plan | IFR |
| Aircraft 2 | |
| Controlling Facilities | tower : bna.tower |
| Make Model Name | Fighter |
| Operating Under FAR Part | Part 91 |
| Flight Phase | descent : approach |
| Person 1 | |
| Affiliation | company : air carrier |
| Function | flight crew : first officer |
| Qualification | pilot : atp |
| Experience | flight time last 90 days : 180 flight time total : 6500 flight time type : 1600 |
| ASRS Report | 518165 |
| Person 2 | |
| Affiliation | company : air carrier |
| Function | flight crew : captain oversight : pic |
| Events | |
| Anomaly | conflict : ground less severe inflight encounter : weather non adherence : clearance non adherence : required legal separation non adherence : published procedure |
| Independent Detector | other controllera |
| Resolutory Action | controller : issued new clearance controller : issued advisory flight crew : executed go around |
| Consequence | faa : reviewed incident with flight crew other |
| Supplementary | |
| Problem Areas | Aircraft Airport Environmental Factor Flight Crew Human Performance Navigational Facility |
| Primary Problem | Flight Crew Human Performance |
| Air Traffic Incident | Pilot Deviation |
Narrative:
This event occurred on taxi out from bna. On rounding the corner at the end of the terminal area, I contacted ground for taxi. Ground gave us taxi instruction to runway 2L. I selected this runway in the opc and found that due to our weight, that a bleeds off takeoff would be required. Since our APU was inoperative and it was hot, we decided to ask for runway 31. I contacted ground control again with our request for runway 31 and stated it was for operational necessity. Ground then gave us instructions to 'exit T6 to runway 31.' as this clearance did not state the 'hold short' instructions on our 10-7 page, we taxied to the closer hold short line. As we waited for takeoff clearance, we noticed an F86 on a long final for runway 31. The tower then notified the F86 that runway 31 was no longer available and issued circling instructions to runway 2R. We were late cleared for takeoff. On departure, the captain asked the tower why the runway was no longer available for the F86 to land. Tower stated that our position was too close to the runway for the F86 to land and commented on the instrument hold short line as being the appropriate place to hold short. The taxi/runway markings for this runway is very confusing. In the absence of a specific clearance to hold at the 'instrument hold line' it is only natural to taxi up to the next line that is 90 degrees to the runway.
Original NASA ASRS Text
Title: A B737-300 FLC CAUSES AN F86 ACFT TO GO AROUND WHEN THEY TAXI PAST THE PRIMARY DESIGNATED APCH HOLD SHORT LINE FOR RWY 31 AT BNA, TN.
Narrative: THIS EVENT OCCURRED ON TAXI OUT FROM BNA. ON ROUNDING THE CORNER AT THE END OF THE TERMINAL AREA, I CONTACTED GND FOR TAXI. GND GAVE US TAXI INSTRUCTION TO RWY 2L. I SELECTED THIS RWY IN THE OPC AND FOUND THAT DUE TO OUR WT, THAT A BLEEDS OFF TKOF WOULD BE REQUIRED. SINCE OUR APU WAS INOP AND IT WAS HOT, WE DECIDED TO ASK FOR RWY 31. I CONTACTED GND CTL AGAIN WITH OUR REQUEST FOR RWY 31 AND STATED IT WAS FOR OPERATIONAL NECESSITY. GND THEN GAVE US INSTRUCTIONS TO 'EXIT T6 TO RWY 31.' AS THIS CLRNC DID NOT STATE THE 'HOLD SHORT' INSTRUCTIONS ON OUR 10-7 PAGE, WE TAXIED TO THE CLOSER HOLD SHORT LINE. AS WE WAITED FOR TKOF CLRNC, WE NOTICED AN F86 ON A LONG FINAL FOR RWY 31. THE TWR THEN NOTIFIED THE F86 THAT RWY 31 WAS NO LONGER AVAILABLE AND ISSUED CIRCLING INSTRUCTIONS TO RWY 2R. WE WERE LATE CLRED FOR TKOF. ON DEP, THE CAPT ASKED THE TWR WHY THE RWY WAS NO LONGER AVAILABLE FOR THE F86 TO LAND. TWR STATED THAT OUR POS WAS TOO CLOSE TO THE RWY FOR THE F86 TO LAND AND COMMENTED ON THE INST HOLD SHORT LINE AS BEING THE APPROPRIATE PLACE TO HOLD SHORT. THE TAXI/RWY MARKINGS FOR THIS RWY IS VERY CONFUSING. IN THE ABSENCE OF A SPECIFIC CLRNC TO HOLD AT THE 'INST HOLD LINE' IT IS ONLY NATURAL TO TAXI UP TO THE NEXT LINE THAT IS 90 DEGS TO THE RWY.
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.