|37000 Feet||Browse and search NASA's
Aviation Safety Reporting System
|Local Time Of Day||0601 To 1200|
|Locale Reference||airport : frr.airport|
|Controlling Facilities||tracon : pct.tracon|
|Operator||general aviation : personal|
|Make Model Name||Skyhawk 172/Cutlass 172|
|Operating Under FAR Part||Part 91|
|Flight Phase||cruise : level|
|Function||flight crew : single pilot|
|Qualification||pilot : multi engine|
pilot : commercial
pilot : instrument
|Experience||flight time last 90 days : 12|
flight time total : 500
flight time type : 200
|Affiliation||government : faa|
|Function||controller : approach|
|Anomaly||airspace violation : entry|
non adherence : published procedure
non adherence : far
|Independent Detector||other controllera|
|Resolutory Action||controller : issued advisory|
|Consequence||faa : reviewed incident with flight crew|
faa : investigated
|Problem Areas||Flight Crew Human Performance|
|Primary Problem||Flight Crew Human Performance|
|Air Traffic Incident||Pilot Deviation|
I conducted a flight from martinsburg, wv (mrb), to frederick, md (fdk), to hagerstown, md (hgr), to martinsburg, wv (mrb). This was my first flight into the area as I had just returned to flying upon retiring and had been renewing my flying skills. The planning for the flight began the previous evening when I charted the route, upgraded the software on my GPS and purchased the commercial chart update to the database. I noticed that the leg from fdk to hgr came within a couple of mi, but did not enter R-4009 around camp david. I planned to stay well west of my course to ensure no entry into R-4009. I called elkins FSS for a briefing and was advised that the temporary tfr around camp david was in effect. I asked him if it was 10 NM. He responded that yes it was 10 NM. Unfortunately, I thought that the tfr was a 10 NM diameter around camp david, and unfortunately the briefer did not specifically advise me that it was a 10 NM radius from camp david. I went to my chart and measured R-4009 to ensure it was 10 NM in diameter. So R-4009 must be the outline for the tfr. As I flew the leg from mrb to fdk, I monitored 121.5 as I knew I would be flying within about 6 NM of the washington ADIZ. After a touch-and-go at fdk, I picked up the route to hgr and, as planned, I stayed a few mi west of my course to avoid the tfr which I believed to be represented on the chart and my GPS as the outline of R-4009. After a few mins in the air, I heard potomac approach on 121.5 advising the aircraft over I-70 at 2300 ft, squawking 1200 that the aircraft was about to enter an ADIZ. Understanding that he must be calling me and believing I had somehow gotten too far south into washington ADIZ, I immediately turned north for a couple of mins, before resuming a northwesterly course for hgr. However, I must have been approaching the camp david tfr and not the washington ADIZ, so my turn to the north actually put me into the restr airspace. When I contacted hagerstown tower, I was advised that I was right on the edge of a tfr and to turn immediately west. I changed course to the west and was then directed back to hgr for landing. As I left hgr for mrb, the tower gave me a phone number to call when I arrived at mrb. The number was for potomac TRACON and the controller told me that when I had abruptly turned north I had gone about 1 mi into the camp david tfr.
Original NASA ASRS Text
Title: A C172 PLT MADE SOME INCORRECT ASSUMPTIONS AND VIOLATED THE CAMP DAVID TFR.
Narrative: I CONDUCTED A FLT FROM MARTINSBURG, WV (MRB), TO FREDERICK, MD (FDK), TO HAGERSTOWN, MD (HGR), TO MARTINSBURG, WV (MRB). THIS WAS MY FIRST FLT INTO THE AREA AS I HAD JUST RETURNED TO FLYING UPON RETIRING AND HAD BEEN RENEWING MY FLYING SKILLS. THE PLANNING FOR THE FLT BEGAN THE PREVIOUS EVENING WHEN I CHARTED THE RTE, UPGRADED THE SOFTWARE ON MY GPS AND PURCHASED THE COMMERCIAL CHART UPDATE TO THE DATABASE. I NOTICED THAT THE LEG FROM FDK TO HGR CAME WITHIN A COUPLE OF MI, BUT DID NOT ENTER R-4009 AROUND CAMP DAVID. I PLANNED TO STAY WELL W OF MY COURSE TO ENSURE NO ENTRY INTO R-4009. I CALLED ELKINS FSS FOR A BRIEFING AND WAS ADVISED THAT THE TEMPORARY TFR AROUND CAMP DAVID WAS IN EFFECT. I ASKED HIM IF IT WAS 10 NM. HE RESPONDED THAT YES IT WAS 10 NM. UNFORTUNATELY, I THOUGHT THAT THE TFR WAS A 10 NM DIAMETER AROUND CAMP DAVID, AND UNFORTUNATELY THE BRIEFER DID NOT SPECIFICALLY ADVISE ME THAT IT WAS A 10 NM RADIUS FROM CAMP DAVID. I WENT TO MY CHART AND MEASURED R-4009 TO ENSURE IT WAS 10 NM IN DIAMETER. SO R-4009 MUST BE THE OUTLINE FOR THE TFR. AS I FLEW THE LEG FROM MRB TO FDK, I MONITORED 121.5 AS I KNEW I WOULD BE FLYING WITHIN ABOUT 6 NM OF THE WASHINGTON ADIZ. AFTER A TOUCH-AND-GO AT FDK, I PICKED UP THE RTE TO HGR AND, AS PLANNED, I STAYED A FEW MI W OF MY COURSE TO AVOID THE TFR WHICH I BELIEVED TO BE REPRESENTED ON THE CHART AND MY GPS AS THE OUTLINE OF R-4009. AFTER A FEW MINS IN THE AIR, I HEARD POTOMAC APCH ON 121.5 ADVISING THE ACFT OVER I-70 AT 2300 FT, SQUAWKING 1200 THAT THE ACFT WAS ABOUT TO ENTER AN ADIZ. UNDERSTANDING THAT HE MUST BE CALLING ME AND BELIEVING I HAD SOMEHOW GOTTEN TOO FAR S INTO WASHINGTON ADIZ, I IMMEDIATELY TURNED N FOR A COUPLE OF MINS, BEFORE RESUMING A NORTHWESTERLY COURSE FOR HGR. HOWEVER, I MUST HAVE BEEN APCHING THE CAMP DAVID TFR AND NOT THE WASHINGTON ADIZ, SO MY TURN TO THE N ACTUALLY PUT ME INTO THE RESTR AIRSPACE. WHEN I CONTACTED HAGERSTOWN TWR, I WAS ADVISED THAT I WAS RIGHT ON THE EDGE OF A TFR AND TO TURN IMMEDIATELY W. I CHANGED COURSE TO THE W AND WAS THEN DIRECTED BACK TO HGR FOR LNDG. AS I LEFT HGR FOR MRB, THE TWR GAVE ME A PHONE NUMBER TO CALL WHEN I ARRIVED AT MRB. THE NUMBER WAS FOR POTOMAC TRACON AND THE CTLR TOLD ME THAT WHEN I HAD ABRUPTLY TURNED N I HAD GONE ABOUT 1 MI INTO THE CAMP DAVID TFR.
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.