Narrative:

On departure from bwg, I received clearance (IFR) from lou radio for flight from bwg to bna. The PF was monitoring the CTAF for bwg (123.0 MHZ) while I was obtaining our IFR clearance on #2 VHF. Lou radio issued our IFR clearance 'cleared to bna as filed. Climb and maintain 6000 ft, contact ZME on 133.85 MHZ.' I had filed the flight plan earlier in the day with routing, bwg direct to bna. The PF set up the FMS route anticipating routing over hehaw intersection, and although we had reviewed the departure, neither pilot caught the discrepancy between our filed route and the FMS routing. This resulted in an excursion from the cleared route that caused concern for the ZME controller. He had inbound traffic to hehaw at our altitude. The controller clarified our routing and issued a heading change to us. Horizontal separation remained greater than 5 NM, according to our TCASII display, through the entire scenario. This was a classic case of crew communication deficiency brought on in part by the PF monitoring a CTAF at an uncontrolled airport while the PNF used another frequency to obtain the IFR clearance. Our company procedures were followed for operations at uncontrolled airports in which the PF monitors the CTAF for local traffic while his copilot uses the other VHF transceiver to obtain the IFR clearance. In this instance, safety was compromised with the initial error being in the programming of the FMS flight plan with a routing other than that filed before the clearance was received. Supplemental information from acn 457730: our FMS was set up for the hehaw 3 arrival from bwg to hehaw to bna. When we departed runway 21 at bwg, we turned right to a heading of 245 degrees to proceed direct to hehaw intersection instead of flying direct to bna. Traffic was given at our altitude (10000 ft) and 7 or 8 mi at our 11 O'clock position. When we advised the traffic in sight we were given a clearance to maintain a visual separation and fly direct to bna. The traffic did not come within 5 mi of our aircraft.

Google
 

Original NASA ASRS Text

Title: A FALCON 50 CPR ACFT FLIES THE WRONG DIRECTION AFTER DEPARTING BWG AND HAS TO RECEIVE A COURSE CORRECTION TO AVOID OTHER TFC BY ZME, TN.

Narrative: ON DEP FROM BWG, I RECEIVED CLRNC (IFR) FROM LOU RADIO FOR FLT FROM BWG TO BNA. THE PF WAS MONITORING THE CTAF FOR BWG (123.0 MHZ) WHILE I WAS OBTAINING OUR IFR CLRNC ON #2 VHF. LOU RADIO ISSUED OUR IFR CLRNC 'CLRED TO BNA AS FILED. CLB AND MAINTAIN 6000 FT, CONTACT ZME ON 133.85 MHZ.' I HAD FILED THE FLT PLAN EARLIER IN THE DAY WITH ROUTING, BWG DIRECT TO BNA. THE PF SET UP THE FMS RTE ANTICIPATING ROUTING OVER HEHAW INTXN, AND ALTHOUGH WE HAD REVIEWED THE DEP, NEITHER PLT CAUGHT THE DISCREPANCY BTWN OUR FILED RTE AND THE FMS ROUTING. THIS RESULTED IN AN EXCURSION FROM THE CLRED RTE THAT CAUSED CONCERN FOR THE ZME CTLR. HE HAD INBOUND TFC TO HEHAW AT OUR ALT. THE CTLR CLARIFIED OUR ROUTING AND ISSUED A HDG CHANGE TO US. HORIZ SEPARATION REMAINED GREATER THAN 5 NM, ACCORDING TO OUR TCASII DISPLAY, THROUGH THE ENTIRE SCENARIO. THIS WAS A CLASSIC CASE OF CREW COM DEFICIENCY BROUGHT ON IN PART BY THE PF MONITORING A CTAF AT AN UNCTLED ARPT WHILE THE PNF USED ANOTHER FREQ TO OBTAIN THE IFR CLRNC. OUR COMPANY PROCS WERE FOLLOWED FOR OPS AT UNCTLED ARPTS IN WHICH THE PF MONITORS THE CTAF FOR LCL TFC WHILE HIS COPLT USES THE OTHER VHF TRANSCEIVER TO OBTAIN THE IFR CLRNC. IN THIS INSTANCE, SAFETY WAS COMPROMISED WITH THE INITIAL ERROR BEING IN THE PROGRAMMING OF THE FMS FLT PLAN WITH A ROUTING OTHER THAN THAT FILED BEFORE THE CLRNC WAS RECEIVED. SUPPLEMENTAL INFO FROM ACN 457730: OUR FMS WAS SET UP FOR THE HEHAW 3 ARR FROM BWG TO HEHAW TO BNA. WHEN WE DEPARTED RWY 21 AT BWG, WE TURNED R TO A HDG OF 245 DEGS TO PROCEED DIRECT TO HEHAW INTXN INSTEAD OF FLYING DIRECT TO BNA. TFC WAS GIVEN AT OUR ALT (10000 FT) AND 7 OR 8 MI AT OUR 11 O'CLOCK POS. WHEN WE ADVISED THE TFC IN SIGHT WE WERE GIVEN A CLRNC TO MAINTAIN A VISUAL SEPARATION AND FLY DIRECT TO BNA. THE TFC DID NOT COME WITHIN 5 MI OF OUR ACFT.

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.