Narrative:

I departed rdu on the morning of feb/wed/04 on a flight to lhz with a safety pilot to practice approachs. The departure from rdu took us near a tfr located within the rdu class C airspace. I obtained a WX briefing about XA30. WX was VFR with nothing significant in the area. Around XD45, about 15 mins before departure, I called FSS and requested a standard briefing. The briefer started by saying that a tfr had just popped up. He proceeded with the standard briefing. When he returned to the tfr, he gave the following details. Clearance delivery specified a departure altitude of 3000 ft instead of the usual 2000 ft. We assumed ATC had the tfr information based on this change. We were cleared to depart runway 23L with a departure heading of 180 degrees. We flew this heading while climbing to 3000 ft. Departure control instructed us to proceed to lhz. I informed departure of our request for the approachs and requested flight following. Rdu departure control provided assistance with the approachs at lhz. We flew several approachs at lhz and jnx before returning to rdu. I looked at the graphical version of the tfr after returning to raleigh. The tfr appeared further south than the verbal description indicated. In reviewing the flight, I believe the controller, while keeping us out of the tfr, placed us very close. Given the significance of a tfr, I think it would be useful for ATC to communicate that they are in fact providing vectors around a tfr, especially in terminal areas, while on an IFR flight plan or VFR with flight following. This would also help pilots avoid a tfr issued while in-flight.

Related reports:

Google
 

Original NASA ASRS Text

Title: C172 DEP FROM RDU IS CONCERNED WITH ATC VECTORS NEAR TFR.

Narrative: I DEPARTED RDU ON THE MORNING OF FEB/WED/04 ON A FLT TO LHZ WITH A SAFETY PLT TO PRACTICE APCHS. THE DEP FROM RDU TOOK US NEAR A TFR LOCATED WITHIN THE RDU CLASS C AIRSPACE. I OBTAINED A WX BRIEFING ABOUT XA30. WX WAS VFR WITH NOTHING SIGNIFICANT IN THE AREA. AROUND XD45, ABOUT 15 MINS BEFORE DEP, I CALLED FSS AND REQUESTED A STANDARD BRIEFING. THE BRIEFER STARTED BY SAYING THAT A TFR HAD JUST POPPED UP. HE PROCEEDED WITH THE STANDARD BRIEFING. WHEN HE RETURNED TO THE TFR, HE GAVE THE FOLLOWING DETAILS. CLRNC DELIVERY SPECIFIED A DEP ALT OF 3000 FT INSTEAD OF THE USUAL 2000 FT. WE ASSUMED ATC HAD THE TFR INFO BASED ON THIS CHANGE. WE WERE CLRED TO DEPART RWY 23L WITH A DEP HDG OF 180 DEGS. WE FLEW THIS HDG WHILE CLBING TO 3000 FT. DEP CTL INSTRUCTED US TO PROCEED TO LHZ. I INFORMED DEP OF OUR REQUEST FOR THE APCHS AND REQUESTED FLT FOLLOWING. RDU DEP CTL PROVIDED ASSISTANCE WITH THE APCHS AT LHZ. WE FLEW SEVERAL APCHS AT LHZ AND JNX BEFORE RETURNING TO RDU. I LOOKED AT THE GRAPHICAL VERSION OF THE TFR AFTER RETURNING TO RALEIGH. THE TFR APPEARED FURTHER S THAN THE VERBAL DESCRIPTION INDICATED. IN REVIEWING THE FLT, I BELIEVE THE CTLR, WHILE KEEPING US OUT OF THE TFR, PLACED US VERY CLOSE. GIVEN THE SIGNIFICANCE OF A TFR, I THINK IT WOULD BE USEFUL FOR ATC TO COMMUNICATE THAT THEY ARE IN FACT PROVIDING VECTORS AROUND A TFR, ESPECIALLY IN TERMINAL AREAS, WHILE ON AN IFR FLT PLAN OR VFR WITH FLT FOLLOWING. THIS WOULD ALSO HELP PLTS AVOID A TFR ISSUED WHILE INFLT.

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.