Narrative:

Air carrier X was shipped to my sector by ZJX. Non radar pilot reported on frequency, requesting direct gtk (a turn to his left). I advised him that I was unable due to non radar airspace to his left, approximately 20 mi. The pilot then said he was deviating for WX to his left. I told him unable again due to the airspace and approved a deviation to the right. The captain refused to turn away from the airspace and entered it. I called new york and told them about the aircraft and also told my supervisor what had happened. New york blocked FL310. The actions of this aircraft resulted in me having to relay through air carrier Y and air carrier Z, in order to try and plot the aircraft's movement using latitude/longitude and crossing airways. The aircraft also prevented another air carrier from getting his requested altitude due to air carrier X having the altitude blocked. WX sat did not show WX that would require a deviation so drastic as what was done. The aircraft was radar idented 50 mi inside new york's airspace. The actions of the captain of air carrier X resulted in a degradation of safety for himself and delays for any other user. Interestingly, the flight path taken by air carrier X was almost a direct route to gtk from where he first asked and where he was idented.

Google
 

Original NASA ASRS Text

Title: PLTDEV WHEN FLC TURNED L TO AVOID WX AGAINST CTLR'S INSTRUCTIONS AND ENTERED NON RADAR AIRSPACE REQUIRING INTERFAC COORD WITH ZNY. ACTION REQUIRED ZNY TO BLOCK THE ALT WHICH AFFECTED ANOTHER ACFT REQUESTING THE SAME ALT OF FL310. RPTR HAD TO USE OTHER ACFT TO COMMUNICATE WITH ACR X TO PLOT ACFT'S MOVEMENT USING LATITUDE LONGITUDE AND XING AIRWAYS. RPTR ALLEGES THE TURN PUT THE ACFT ALMOST ON A DIRECT RTE TOWARD GTK WHICH THE PLT HAD INITIALLY REQUESTED PRIOR TO THE DEV.

Narrative: ACR X WAS SHIPPED TO MY SECTOR BY ZJX. NON RADAR PLT RPTED ON FREQ, REQUESTING DIRECT GTK (A TURN TO HIS L). I ADVISED HIM THAT I WAS UNABLE DUE TO NON RADAR AIRSPACE TO HIS L, APPROX 20 MI. THE PLT THEN SAID HE WAS DEVIATING FOR WX TO HIS L. I TOLD HIM UNABLE AGAIN DUE TO THE AIRSPACE AND APPROVED A DEV TO THE R. THE CAPT REFUSED TO TURN AWAY FROM THE AIRSPACE AND ENTERED IT. I CALLED NEW YORK AND TOLD THEM ABOUT THE ACFT AND ALSO TOLD MY SUPVR WHAT HAD HAPPENED. NEW YORK BLOCKED FL310. THE ACTIONS OF THIS ACFT RESULTED IN ME HAVING TO RELAY THROUGH ACR Y AND ACR Z, IN ORDER TO TRY AND PLOT THE ACFT'S MOVEMENT USING LATITUDE/LONGITUDE AND XING AIRWAYS. THE ACFT ALSO PREVENTED ANOTHER ACR FROM GETTING HIS REQUESTED ALT DUE TO ACR X HAVING THE ALT BLOCKED. WX SAT DID NOT SHOW WX THAT WOULD REQUIRE A DEV SO DRASTIC AS WHAT WAS DONE. THE ACFT WAS RADAR IDENTED 50 MI INSIDE NEW YORK'S AIRSPACE. THE ACTIONS OF THE CAPT OF ACR X RESULTED IN A DEGRADATION OF SAFETY FOR HIMSELF AND DELAYS FOR ANY OTHER USER. INTERESTINGLY, THE FLT PATH TAKEN BY ACR X WAS ALMOST A DIRECT RTE TO GTK FROM WHERE HE FIRST ASKED AND WHERE HE WAS IDENTED.

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.