Narrative:

Company filed flight plan showed routing ric direct ott direct bwi, written 'ric...ott...bwi' on cockpit flight papers. Washington center was alarmed, gave immediate turns and descent clearance for traffic avoidance. Clearance according to ATC, was 'ric...OTT1...bwi.' a major dogleg right is involved in the 'nottingham 1 arrival.' are keystrokes lost in transmission? (Note: we were never verbally cleared by washington center to fly the OTT1 arrival). Notified company dispatch of incident and probable cause. Suggestion: avoid using name such as 'nottingham 1' for arrival procedures. Instead, avoid chance of misunderstanding by using unrelated name--example: 'maryland 1 arrival.' then no chance that ric...OTT1...bwi could be transmitted as ric...ott...bwi.

Related reports:

Google
 

Original NASA ASRS Text

Title: ACR LGT DEVIATED FROM COMPANY FILED FLT PLAN. THE FLT CREW'S COPY WAS NOT CONSISTENT WITH THE ROUTING FILED WITH ATC.

Narrative: COMPANY FILED FLT PLAN SHOWED ROUTING RIC DIRECT OTT DIRECT BWI, WRITTEN 'RIC...OTT...BWI' ON COCKPIT FLT PAPERS. WASHINGTON CTR WAS ALARMED, GAVE IMMEDIATE TURNS AND DSCNT CLRNC FOR TFC AVOIDANCE. CLRNC ACCORDING TO ATC, WAS 'RIC...OTT1...BWI.' A MAJOR DOGLEG RIGHT IS INVOLVED IN THE 'NOTTINGHAM 1 ARR.' ARE KEYSTROKES LOST IN XMISSION? (NOTE: WE WERE NEVER VERBALLY CLRED BY WASHINGTON CTR TO FLY THE OTT1 ARR). NOTIFIED COMPANY DISPATCH OF INCIDENT AND PROBABLE CAUSE. SUGGESTION: AVOID USING NAME SUCH AS 'NOTTINGHAM 1' FOR ARR PROCS. INSTEAD, AVOID CHANCE OF MISUNDERSTANDING BY USING UNRELATED NAME--EXAMPLE: 'MARYLAND 1 ARRIVAL.' THEN NO CHANCE THAT RIC...OTT1...BWI COULD BE TRANSMITTED AS RIC...OTT...BWI.

Data retrieved from NASA's ASRS site as of August 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.