A corporate pilot reported that after departing a chicago area airport; an airborne weather reroute ...

Attributes
ACN	1030546
Time
Date	201208
Local Time Of Day	0601-1200
Place
Locale Reference	ZAU.ARTCC
State Reference	IL
Environment
Flight Conditions	Mixed
Light	Daylight
Aircraft 1
Make Model Name	Light Transport Low Wing 2 Turbojet Eng
Operating Under FAR Part	Part 91
Flight Phase	Climb
Route In Use	Direct
Flight Plan	IFR
Component
Aircraft Component	FMS/FMC
Person 1
Function	Pilot Not Flying First Officer
Qualification	Flight Crew Multiengine Flight Crew Air Transport Pilot (ATP) Flight Crew Instrument
Experience	Flight Crew Last 90 Days 80 Flight Crew Total 10000 Flight Crew Type 2200
Events
Anomaly	ATC Issue All Types Deviation - Procedural Clearance Deviation - Track / Heading All Types

Narrative:

ATC center controller gave us rapid fire reroute. Spelled out fixes faster than an auctioneer. He said padde; I thought he said paddy. When I selected and checked relative position (the does it make sense rule) with the weather east it look plausible. I then advised the pilot flying it looked good. He said okay execute direct. This provided a right turn of about 30 degrees. In about 5 minutes the controller asked for the heading. I reponded 130. He said you should be heading around 090; fly heading 090. I started investigating; he asked are you paddy yet. I told him standby. Then asked him to clarify phonetic of padde. Called him back and declared now direct padde. He was a bit rude about the whole thing. He didn't consider that he was oversaturated and was speaking in tones that were so rushed he was difficult to understand. Next time this happens I will ask for initial vectors; look it up on the chart and ask him to verify. Won't go direct until I am sure.

Original NASA ASRS Text

Title: A corporate pilot reported that after departing a Chicago area airport; an airborne weather reroute included PADDE intersection; but PADDY was inserted in the FMC. The track deviation was detected by ATC who then clarified the fix's spelling.

Narrative: ATC Center Controller gave us rapid fire reroute. Spelled out fixes faster than an auctioneer. He said PADDE; I thought he said PADDY. When I selected and checked relative position (the does it make sense rule) with the weather east it look plausible. I then advised the pilot flying it looked good. He said okay execute direct. This provided a right turn of about 30 degrees. In about 5 minutes the Controller asked for the heading. I reponded 130. He said you should be heading around 090; fly heading 090. I started investigating; he asked are you PADDY yet. I told him standby. Then asked him to clarify phonetic of PADDE. Called him back and declared now direct PADDE. He was a bit rude about the whole thing. He didn't consider that he was oversaturated and was speaking in tones that were so rushed he was difficult to understand. Next time this happens I will ask for initial vectors; look it up on the chart and ask him to verify. Won't go direct until I am sure.

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

A corporate pilot reported that after departing a chicago area airport; an airborne weather reroute included padde intersection; but paddy was inserted in the FMC. The track deviation was detected by ATC who then clarified the fix's spelling.