37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 622085 |
Time | |
Date | 200406 |
Day | Wed |
Local Time Of Day | 1801 To 2400 |
Place | |
Locale Reference | airport : bna.airport |
State Reference | TN |
Altitude | msl bound lower : 1700 msl bound upper : 2500 |
Environment | |
Flight Conditions | Marginal |
Light | Night |
Aircraft 1 | |
Controlling Facilities | tracon : bna.tracon tower : bna.tower |
Operator | common carrier : air taxi |
Make Model Name | Baron 58/58TC |
Operating Under FAR Part | Part 135 |
Flight Phase | descent : intermediate altitude descent : approach |
Route In Use | approach : visual arrival : on vectors |
Flight Plan | IFR |
Aircraft 2 | |
Controlling Facilities | tracon : bna.tracon |
Operator | common carrier : air carrier |
Make Model Name | B737 Undifferentiated or Other Model |
Operating Under FAR Part | Part 121 |
Navigation In Use | ils localizer & glide slope : 20l |
Flight Phase | descent : intermediate altitude descent : approach |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air taxi |
Function | flight crew : single pilot |
Qualification | pilot : multi engine pilot : atp pilot : instrument pilot : commercial |
Experience | flight time last 90 days : 240 flight time total : 3000 flight time type : 500 |
ASRS Report | 622085 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Events | |
Anomaly | conflict : airborne critical inflight encounter : vfr in imc non adherence : far non adherence : clearance non adherence : required legal separation other spatial deviation |
Independent Detector | atc equipment : conflict alert other controllera |
Resolutory Action | controller : issued alert flight crew : took precautionary avoidance action |
Miss Distance | vertical : 300 |
Supplementary | |
Problem Areas | Weather Flight Crew Human Performance ATC Human Performance Environmental Factor |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Inter Facility Coordination Failure Pilot Deviation |
Narrative:
I was on my regularly scheduled run for XXX, a part 135 cargo carrier, returning to bna at about XA10. I was being vectored in for a possible visual approach to runway 20L. Approach had me on a westerly heading, and was descending me to see if I could make the visual. I exited the clouds at approximately 2000 ft MSL and began to look for the airport. I got a visual on the airport, and called it in sight, and was cleared for the visual to runway 20L. Considering landmarks observed upon exiting the clouds, I was over 8 NM from the airport and very near the final approach course to runway 20L. As I maneuvered for the visual approach in a descending turn, I received a handoff to nashville tower. At this point no other traffic was pointed out to me, and no specific heading or altitude was assigned. When I switched over to tower, I told them I was on the visual to runway 20L and requested runway 20C. Tower told me to immediately descend to 1500 ft and turn to an easterly heading. Tower then pointed out the B737 to me and asked if I had traffic in sight. I advised tower when I got the traffic in sight (I only saw landing lights from within the clouds approximately 300+ ft above me, about 2000 ft MSL). I was then cleared for the visual runway 20C and landed without further incident. I believe that the problem arose due to the marginal WX and the attempts at getting visual approachs in marginal WX. Another factor was that no traffic was ever pointed out to me, no heading or altitude assigned, and no advisory that I had overshot the extended centerline of runway 20L until it became a problem. Personally, in hindsight, it probably would have been better to line all aircraft on the localizer to better keep them separated. Another solution would be to point out traffic before clearing me for the visual. Supplemental information from acn 622908: I was flying XXX123 (my regular part 135 flight) into bna. Approaching from the southeast, I observed a deck of clouds over bna with ceilings around 2000 ft AGL and no restrs to visibility. While under the control of nashville approach, I heard air taxi X check on and saw him behind me. Subsequently, an air carrier Y (a B737), checked on. As I neared bna, I spotted the airport and was cleared for a visual approach. At this point, I observed air taxi X approximately 4 NM to my north, 1000 ft above me, maintaining his last assigned heading. ATC then asked the crew of the B737 if they would like to try a visual approach. The B737 air carrier Y, previously being vectored to an ILS, elected to attempt a visual approach. They requested different runways numerous times and were having trouble making visual contact with the airport. It seemed the controllers were preoccupied with the B737, as they were vectored for numerous turns and queried about whether or not they wanted to proceed with a visual approach or fly an ILS. I was handed over to the tower controller and cleared to land, however, I continued to monitor the approach frequency on my secondary radio. I head air taxi X report the airport in sight, and the approach controller clear him for the visual approach. At this time, the crew of the B737 reported IMC and was turned off their course. I landed uneventfully. Taxiing to the ramp, I observed the tower controller order air taxi X to execute a rapid descent to 1500 ft MSL and change heading. The crew of the B737 again called IMC.
Original NASA ASRS Text
Title: 3 ACFT -- A BE58, A B737, AND A C210 ALL ATTEMPT TO FLY VISUAL APCHS TO BNA WITH MARGINAL WX. LCL CTLR MUST INTERVENE TO PREVENT NMAC BTWN THE B737 AND THE BE58.
Narrative: I WAS ON MY REGULARLY SCHEDULED RUN FOR XXX, A PART 135 CARGO CARRIER, RETURNING TO BNA AT ABOUT XA10. I WAS BEING VECTORED IN FOR A POSSIBLE VISUAL APCH TO RWY 20L. APCH HAD ME ON A WESTERLY HDG, AND WAS DSNDING ME TO SEE IF I COULD MAKE THE VISUAL. I EXITED THE CLOUDS AT APPROX 2000 FT MSL AND BEGAN TO LOOK FOR THE ARPT. I GOT A VISUAL ON THE ARPT, AND CALLED IT IN SIGHT, AND WAS CLRED FOR THE VISUAL TO RWY 20L. CONSIDERING LANDMARKS OBSERVED UPON EXITING THE CLOUDS, I WAS OVER 8 NM FROM THE ARPT AND VERY NEAR THE FINAL APCH COURSE TO RWY 20L. AS I MANEUVERED FOR THE VISUAL APCH IN A DSNDING TURN, I RECEIVED A HDOF TO NASHVILLE TWR. AT THIS POINT NO OTHER TFC WAS POINTED OUT TO ME, AND NO SPECIFIC HDG OR ALT WAS ASSIGNED. WHEN I SWITCHED OVER TO TWR, I TOLD THEM I WAS ON THE VISUAL TO RWY 20L AND REQUESTED RWY 20C. TWR TOLD ME TO IMMEDIATELY DSND TO 1500 FT AND TURN TO AN EASTERLY HDG. TWR THEN POINTED OUT THE B737 TO ME AND ASKED IF I HAD TFC IN SIGHT. I ADVISED TWR WHEN I GOT THE TFC IN SIGHT (I ONLY SAW LNDG LIGHTS FROM WITHIN THE CLOUDS APPROX 300+ FT ABOVE ME, ABOUT 2000 FT MSL). I WAS THEN CLRED FOR THE VISUAL RWY 20C AND LANDED WITHOUT FURTHER INCIDENT. I BELIEVE THAT THE PROB AROSE DUE TO THE MARGINAL WX AND THE ATTEMPTS AT GETTING VISUAL APCHS IN MARGINAL WX. ANOTHER FACTOR WAS THAT NO TFC WAS EVER POINTED OUT TO ME, NO HDG OR ALT ASSIGNED, AND NO ADVISORY THAT I HAD OVERSHOT THE EXTENDED CTRLINE OF RWY 20L UNTIL IT BECAME A PROB. PERSONALLY, IN HINDSIGHT, IT PROBABLY WOULD HAVE BEEN BETTER TO LINE ALL ACFT ON THE LOC TO BETTER KEEP THEM SEPARATED. ANOTHER SOLUTION WOULD BE TO POINT OUT TFC BEFORE CLRING ME FOR THE VISUAL. SUPPLEMENTAL INFO FROM ACN 622908: I WAS FLYING XXX123 (MY REGULAR PART 135 FLT) INTO BNA. APCHING FROM THE SE, I OBSERVED A DECK OF CLOUDS OVER BNA WITH CEILINGS AROUND 2000 FT AGL AND NO RESTRS TO VISIBILITY. WHILE UNDER THE CTL OF NASHVILLE APCH, I HEARD AIR TAXI X CHK ON AND SAW HIM BEHIND ME. SUBSEQUENTLY, AN ACR Y (A B737), CHKED ON. AS I NEARED BNA, I SPOTTED THE ARPT AND WAS CLRED FOR A VISUAL APCH. AT THIS POINT, I OBSERVED AIR TAXI X APPROX 4 NM TO MY N, 1000 FT ABOVE ME, MAINTAINING HIS LAST ASSIGNED HDG. ATC THEN ASKED THE CREW OF THE B737 IF THEY WOULD LIKE TO TRY A VISUAL APCH. THE B737 ACR Y, PREVIOUSLY BEING VECTORED TO AN ILS, ELECTED TO ATTEMPT A VISUAL APCH. THEY REQUESTED DIFFERENT RWYS NUMEROUS TIMES AND WERE HAVING TROUBLE MAKING VISUAL CONTACT WITH THE ARPT. IT SEEMED THE CTLRS WERE PREOCCUPIED WITH THE B737, AS THEY WERE VECTORED FOR NUMEROUS TURNS AND QUERIED ABOUT WHETHER OR NOT THEY WANTED TO PROCEED WITH A VISUAL APCH OR FLY AN ILS. I WAS HANDED OVER TO THE TWR CTLR AND CLRED TO LAND, HOWEVER, I CONTINUED TO MONITOR THE APCH FREQ ON MY SECONDARY RADIO. I HEAD AIR TAXI X RPT THE ARPT IN SIGHT, AND THE APCH CTLR CLR HIM FOR THE VISUAL APCH. AT THIS TIME, THE CREW OF THE B737 RPTED IMC AND WAS TURNED OFF THEIR COURSE. I LANDED UNEVENTFULLY. TAXIING TO THE RAMP, I OBSERVED THE TWR CTLR ORDER AIR TAXI X TO EXECUTE A RAPID DSCNT TO 1500 FT MSL AND CHANGE HDG. THE CREW OF THE B737 AGAIN CALLED IMC.
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.