FLT CREW EXPERIENCES A NAV DEVIATION WHEN THEY WERE CLEARED TO REGGY BUT ENTERED REGGE IN THE FMS.

Date: 2008-05 · Aircraft: Light Transport; Low Wing; 2 Turbojet Eng · Phase: cruise

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

Synopsis

FLT CREW EXPERIENCES A NAV DEVIATION WHEN THEY WERE CLEARED TO REGGY BUT ENTERED REGGE IN THE FMS.

Narrative

THE SIC PICKED UP OUR CLRNC AS FOLLOWS: CLRED TO BWI ARPT VIA PWK2; RADAR VECTORS; ADIME; OTENS; REGGY. THIS WAS WRITTEN ON OUR TOLD CARD AND SIC GAVE READBACK TO CLRNC DELIVERY. AFTER DEPARTING AND REACHING ALT OF FL350; WE WERE GIVEN DIRECT ADIME; FPR. AFTER DEPARTING OTENS; ZAU ASKED FOR OUR HDG AND WANTED TO VERIFY WE WERE NAVING ACCORDING OUR ATC CLRNC. THE SIC ANSWERED WITH; 'AFFIRMATIVE; WE WERE GIVEN REGGY AFTER OTENS AND WE ARE PROCEEDING ACCORDINGLY; BUT WE DO HAVE 105 KTS OF XWIND FROM THE L SO OUR HDG IS REQUIRED TO BE MORE NE DUE TO HIGH WINDS.' CHICAGO RESPONDED; 'YOU WILL NEVER REACH REGGY ON THAT HDG REGARDLESS OF WIND; CHK YOUR SPELLING FOR REGGY.' WE BOTH LOOKED TO VERIFY THAT THE GPS'S FLT PLAN WAS SET ACCORDING TO OUR CLRNC ON OUR TOLD CARD AND WE REALIZED THAT THE SIC HAD ENTERED REGGE INSTEAD OF REGGY AND THE CORRECTION WAS MADE. PROB IS; THE GPS RTE LOOKED NORMAL TO US DUE TO REGGE BEING LOCATED ONLY 30 MI N OF REGGY. CTR ASKED AGAIN IF WE WERE PROCEEDING TO REGGY; THE SIC ANSWERED WITH AN 'AFFIRMATIVE.' CTR DID NOT MENTION ANY TFC CONFLICTS OR CONCERNS. CONTRIBUTION FACTORS: HAVING INTXNS PRONOUNCED THE SAME BUT SPELLED DIFFERENTLY ONLY 30-SOME MI APART CONTRIBUTED TO OUR SITUATION. I CHKED INTO OTHER INTXNS PRONOUNCED THE SAME BUT SPELLED DIFFERENTLY AND FOUND THAT THERE WAS ALSO A REDGE 100 MI TO THE W OF REGGY. I BELIEVE THAT THE CLOSE PROX OF REGGY AND REGGE CONTRIBUTED TO OUR MISTAKE; AND MAY CONTRIBUTE TO FUTURE ACFT ALSO MAKING THE SAME MISTAKE.

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