HDG TRACK DEV BY A B737-200 FLC WHEN UNABLE TO RECEIVE THE DESIGNATED VOR AFTER AN AMENDMENT TO THEIR ROUTING WAS RECEIVED FROM CTLRS AT ZAU.

2004-06 · NASA ASRS report 620479

Date: 2004-06 · Aircraft: B737-200 · Phase: cruise

Anomalies: deviation-track-heading-all-types|deviation-discrepancy-procedural-clearance

Synopsis

HDG TRACK DEV BY A B737-200 FLC WHEN UNABLE TO RECEIVE THE DESIGNATED VOR AFTER AN AMENDMENT TO THEIR ROUTING WAS RECEIVED FROM CTLRS AT ZAU.

Narrative

OUR ORIGINAL FLT PLANNED RTE: ZZZ-J89-KURTZ-VHP-OKK.OKK1-KORD. APCHING IIU (LOUISVILLE VOR) FROM THE S; INDIANAPOLIS CTR REROUTED US TO: DIRECT ROD (ROSEWOOD VOR) TO FWA.OX13-KORD. WE TURNED DIRECT TO ROSEWOOD; AND; ACPHING 100 NM S OF ROD; CHICAGO CTR INSTRUCTED US TO MAINTAIN HDG AND EXPECT DIRECT PNT (PONTIAC VOR; FREQ 109.6)-PLANO-ORD. WE READ BACK THIS SECOND REROUTE; AND; UNDERSTOOD THE CTLR TO SAY 'MAINTAIN PRESENT HDG; AND; EXPECT DIRECT PNT ON THAT HDG.' AT THIS TIME WE WERE APPROX OVERHEAD MIE VOR. OUR PRESENT HDG WAS APPROX 330 DEGS. WE BOTH BEGAN SEARCHING FOR PNT VOR ON OUR CHARTS; SINCE THIS WAS THE FIRST FIX IN OUR REROUTE CLRNC. AS WE WERE STILL TRYING TO LOCATE PNT VOR ON OUR CHARTS; THE CTLR CLRED US TO PNT VOR. NOT BEING FAMILIAR WITH THE ORD AREA; WE ASSUMED THE CTLR WAS REFERRING TO PONTIAC; MICHIGAN. AFTER A COUPLE OF MINUTES HAD PASSED SINCE WE WERE CLRED TO PNT; WE FOUND PNT (FREQ 109.6) ON OUR CHART; BUT DIDN'T REALIZE THIS WAS PONTIAC; ILLINOIS. THE RDMI NEEDLES (WE ARE A /A TYPE ACFT- NON FMS EQUIPPED) SWUNG TO APPROX 10 DEGS; AND; WE WERE STILL SEARCHING FOR THE 'PLANO' FIX ON OUR CHART; WHICH WAS THE SECOND POINT ON OUR REROUTE CLRNC. 2 SITS TO MENTION THAT RELATED TO THIS DEV: FIRST; PONTIAC; MI (PSI 111.0) IS JUST OUTSIDE OF DETROIT; AND WE THOUGHT THIS WAS WHERE THE RDMI NEEDLES WERE POINTING. SECONDLY; JACKSON; MI (JXI) IS ALSO FREQ 109.6; AS IS PNT VOR; AND JXI VOR IS APPROX 50 NM DUE W OF PSI VOR. IN ACTUALITY; THE NEEDLES WERE POINTING TO JXI VOR. WE WERE PREOCCUPIED LOOKING FOR 'PLANO' INTXN ON OUR CHART; WHEN CHICAGO CTR QUERIED US ABOUT WHY WE HAVEN'T STARTED OUR TURN FOR PNT VOR. WE IMMEDIATELY INITIATED A TURN TO THE R WHERE THE RDMI NEEDLES WERE POINTING; WHICH WOULD HAVE BEEN APPROX 50 DEGS HDG CHANGE. AS WE WERE TURNING THROUGH A HDG OF 360 DEGS; I QUERIED THE CTLR IF A 20 DEG HDG WOULD PUT US DIRECT PNT. THE CTLR'S RESPONSE WAS 'IMMEDIATELY TURN L TO A 270 DEG HDG AND DSCND TO FL240.' WE COMPLIED WITH THIS INSTRUCTION. AFTER WE SWITCHED TO THE NEXT CHICAGO CTR CTLR; HE CLRED US AGAIN TO PNT VOR. OUR RDMI NEEDLES WERE STILL POINTING TO JXI VOR. WE QUERIED THE CTLR IF 20 DEGS WAS THE HDG FOR 'PONTIAC'; AND HE SAID 'NO; 270 DEGS.' WE THEN DECLARED OUR VHF NAVS UNUSABLE; AND REQUESTED RADAR VECTORS TO PNT AND PLANO INTXN. THE CTLR THEN STATED THAT THIS MISUNDERSTANDING HAD BEEN A PROB BEFORE; AND TOLD US TO CALL CHICAGO CTR VIA TELEPHONE; WHEN WE ARR IN ORD; WHICH WE DID. LOOKING BACK ON THIS EVENT; OUR MISTAKES WERE TWO FOLD. HAD WE KNOWN THAT PNT WAS A 'LOW' VOR; AND OUR DISTANCE FROM THIS VOR WHEN ACCEPTING THIS CLRNC WAS APPROX 130 NM; WE WOULD HAVE ASKED FOR AN INITIAL HDG TO PNT; UNTIL RECEIVING PROPERLY. SECONDLY; WE DID NOT IDENTIFY PNT'S MORSE CODE. OBVIOUSLY; IF WE HAD TRIED TO IDENTIFY; WE WOULD HAVE HEARD JXI'S VOR IDENTIFIER; AND WOULD NOT HAVE ACCEPTED THE CLRNC WITHOUT AN INITIAL HDG FOR PNT. ACTUALLY; WHEN WE FINALLY ATTEMPTED TO IDENTIFY PNT'S MORSE CODE; WE DID NOT RECEIVE PNT OR JXI'S MORSE CODE; JUST STATIC. OUR BIGGEST LESSON LEARNED FROM ALL OF THIS; IS TO ALWAYS IDENTIFY EVERY FREQ TUNED TO MAKE SURE IT IS THE CORRECT STATION CLRED TO; ESPECIALLY WHEN UNFAMILIAR WITH THE LOCAL AREA (PNT VS JXI VOR). ALSO; WHEN GIVEN A CLRNC TO A 'LOW' ALT VOR/NAVAID; ALWAYS REQUEST AN INITIAL HDG FOR CONFIRMATION. CTLRS ARE ACCUSTOMED TO RNAV EQUIPPED ACFT; AND IT HAS BEEN MY EXPERIENCE THAT THEY GIVE CLEARANCES BASED ON THAT ASSUMPTION.

Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.

Loading the flight search…

Frequently asked questions

How do I search flights by aircraft type on FlightFinder?

Pick an aircraft model — Boeing 737, Airbus A320, A380, Boeing 787 Dreamliner and more — enter your origin airport, and FlightFinder shows every route that plane flies from there with live fares.

Which aircraft types can I filter by?

We support Boeing 737/747/757/767/777/787, the full Airbus A220/A319/A320/A321/A330/A340/A350/A380 family, Embraer E170/E175/E190/E195, Bombardier CRJ and Dash 8, and the ATR 42/72 turboprops.

Is FlightFinder free to use?

Search and schedules are free. Pro ($4.99/month, $39/year, or $99 one-time lifetime) unlocks the enriched flight card — on-time stats, CO₂ per passenger, amenities, live gate & weather — plus My Trips with push alerts.

Where does the route data come from?

Live schedules come from Amadeus, AeroDataBox and Travelpayouts. Observed routes (which aircraft actually flew a given city pair) are crowdsourced from adsb.lol ADS-B data under the Open Database License.