37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 245295 |
Time | |
Date | 199307 |
Day | Fri |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | atc facility : bna |
State Reference | TN |
Altitude | agl bound lower : 0 agl bound upper : 50 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tower : bna tower : bos |
Operator | common carrier : air carrier |
Make Model Name | Large Transport, Low Wing, 3 Turbojet Eng |
Flight Phase | climbout : takeoff |
Flight Plan | IFR |
Aircraft 2 | |
Operator | general aviation : personal |
Make Model Name | Small Aircraft, High Wing, 1 Eng, Fixed Gear |
Flight Phase | descent : approach |
Route In Use | approach : straight in |
Flight Plan | None |
Person 1 | |
Affiliation | government : faa |
Function | controller : local |
Qualification | controller : radar pilot : instrument pilot : private |
Experience | controller non radar : 2 controller radar : 11 flight time last 90 days : 0 flight time total : 260 |
ASRS Report | 245295 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp |
Experience | flight time last 90 days : 190 flight time total : 8800 |
ASRS Report | 245147 |
Events | |
Anomaly | conflict : nmac non adherence : published procedure non adherence : required legal separation non adherence : far |
Independent Detector | other flight crewa |
Resolutory Action | none taken : insufficient time |
Consequence | faa : investigated |
Miss Distance | horizontal : 40 vertical : 30 |
Supplementary | |
Primary Problem | ATC Human Performance |
Air Traffic Incident | Operational Error |
Narrative:
Runways 20L, 20C, 20R designated active. Aircraft (air carrier) frequently request runways 13 or 31 during the summer due to added available length. Called ready runway 31, was taxied into position to hold for traffic landing runway 20R (intersecting runway). Small aircraft Y was also on final to runway 20C (flight path overflies runway 31). Cleared to land, about 1 mi behind the runway 20R arrival, as determined from BRITE radar display. Small aircraft Y was not in sight due to bright, hazy sky conditions. My control plan was to depart air carrier X off runway 31 as soon as the runway 20R arrival cleared the downfield intersection. This would have air carrier X through the arrival path of small aircraft Y prior to small aircraft Y reaching the intersection of runway 31. I made no attempt to determine small aircraft Y's position visually prior to clearing air carrier X for takeoff, expecting from the last known position of small aircraft Y (as determined earlier from the BRITE) that the applicable separation would exist. I looked down to my podium to attend to some strip marking and to log some arrs and departures on the appropriate facility form. When I looked back up, I was startled to see small aircraft Y nearly over-flying air carrier X on takeoff roll. There was no time to issue alternate instructions, and the operations continued with no further incident. Only added awareness of small aircraft Y progress toward his runway, and determining his position visually prior to departing air carrier X would have alleviated this situation. Supplemental information from acn 245147: air carrier X was cleared for takeoff runway 31 at bna. During takeoff roll (at approximately 95 KTS), my copilot called out 'watch out! Look at that!' there was an small aircraft on short final to a perpendicular runway about 100 ft above us, descending. I determined we would not collide and continued the takeoff. That landing traffic was not issued to me at all. Had I known about the small aircraft, I would have delayed our takeoff. The small aircraft was on another tower (bna) frequency. I believe the controller should have issued us that traffic.
Original NASA ASRS Text
Title: MULTIPLE RWY OP INTERSECTING RWYS. ACR X TKOF HAD LTSS, NMAC WITH SMA Y. SYS ERROR.
Narrative: RWYS 20L, 20C, 20R DESIGNATED ACTIVE. ACFT (ACR) FREQUENTLY REQUEST RWYS 13 OR 31 DURING THE SUMMER DUE TO ADDED AVAILABLE LENGTH. CALLED READY RWY 31, WAS TAXIED INTO POS TO HOLD FOR TFC LNDG RWY 20R (INTERSECTING RWY). SMA Y WAS ALSO ON FINAL TO RWY 20C (FLT PATH OVERFLIES RWY 31). CLRED TO LAND, ABOUT 1 MI BEHIND THE RWY 20R ARR, AS DETERMINED FROM BRITE RADAR DISPLAY. SMA Y WAS NOT IN SIGHT DUE TO BRIGHT, HAZY SKY CONDITIONS. MY CTL PLAN WAS TO DEPART ACR X OFF RWY 31 AS SOON AS THE RWY 20R ARR CLRED THE DOWNFIELD INTXN. THIS WOULD HAVE ACR X THROUGH THE ARR PATH OF SMA Y PRIOR TO SMA Y REACHING THE INTXN OF RWY 31. I MADE NO ATTEMPT TO DETERMINE SMA Y'S POS VISUALLY PRIOR TO CLRING ACR X FOR TKOF, EXPECTING FROM THE LAST KNOWN POS OF SMA Y (AS DETERMINED EARLIER FROM THE BRITE) THAT THE APPLICABLE SEPARATION WOULD EXIST. I LOOKED DOWN TO MY PODIUM TO ATTEND TO SOME STRIP MARKING AND TO LOG SOME ARRS AND DEPS ON THE APPROPRIATE FACILITY FORM. WHEN I LOOKED BACK UP, I WAS STARTLED TO SEE SMA Y NEARLY OVER-FLYING ACR X ON TKOF ROLL. THERE WAS NO TIME TO ISSUE ALTERNATE INSTRUCTIONS, AND THE OPS CONTINUED WITH NO FURTHER INCIDENT. ONLY ADDED AWARENESS OF SMA Y PROGRESS TOWARD HIS RWY, AND DETERMINING HIS POS VISUALLY PRIOR TO DEPARTING ACR X WOULD HAVE ALLEVIATED THIS SIT. SUPPLEMENTAL INFO FROM ACN 245147: ACR X WAS CLRED FOR TKOF RWY 31 AT BNA. DURING TKOF ROLL (AT APPROX 95 KTS), MY COPLT CALLED OUT 'WATCH OUT! LOOK AT THAT!' THERE WAS AN SMA ON SHORT FINAL TO A PERPENDICULAR RWY ABOUT 100 FT ABOVE US, DSNDING. I DETERMINED WE WOULD NOT COLLIDE AND CONTINUED THE TKOF. THAT LNDG TFC WAS NOT ISSUED TO ME AT ALL. HAD I KNOWN ABOUT THE SMA, I WOULD HAVE DELAYED OUR TKOF. THE SMA WAS ON ANOTHER TWR (BNA) FREQ. I BELIEVE THE CTLR SHOULD HAVE ISSUED US THAT TFC.
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.