37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 529279 |
Time | |
Date | 200111 |
Day | Mon |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | atc facility : zzz.artcc |
State Reference | US |
Altitude | msl single value : 3500 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tracon : zzz.tracon |
Operator | general aviation : personal |
Make Model Name | Small Aircraft, Low Wing, 1 Eng, Retractable Gear |
Operating Under FAR Part | Part 91 |
Navigation In Use | other |
Flight Plan | None |
Person 1 | |
Affiliation | other |
Function | flight crew : single pilot |
Qualification | pilot : multi engine pilot : private pilot : instrument |
Experience | flight time last 90 days : 30 flight time total : 535 flight time type : 485 |
ASRS Report | 529279 |
Person 2 | |
Affiliation | government : faa |
Function | controller : approach |
Events | |
Anomaly | airspace violation : entry non adherence : published procedure other anomaly other |
Independent Detector | other controllera |
Resolutory Action | none taken : detected after the fact |
Supplementary | |
Problem Areas | FAA Airspace Structure Flight Crew Human Performance |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
On 11/fri/01 I accepted a mission to transport an individual from ZZZ to ZZZ1 on the following monday. I immediately began the preflight work which included gathering the information on fdc NOTAM describing the tfrs around power plants, marking up my charts to clearly identify all of these tfrs, and then creating a route from ZZZ2 to ZZZ3 and returning to ZZZ that would avoid the tfrs. I used graphics provided on a web site to assist in plotting the tfrs. On sunday, at approximately XA00 I called FSS to get an outlook briefing for the next day's flts and received the weather information, but no information on tfr NOTAMS. I filed IFR flight plans for each of the 3 legs I would fly on monday. On monday at XB30 I called FSS to get an updated briefing, but again received no information on tfr NOTAMS. On both of these calls the briefer did not offer, nor did I ask for the tfr NOTAM. I flew the first two legs IFR as filed but when it was time to depart ZZZ1 the aircraft in front of me and I were held by ZZZ1 departure. We both decided to go VFR and were released. Because ZZZ1 departure was busy I proceeded north without contacting them. When I was north of ZZZ1 class B space I turned northwest to clear ZZZ4 class C to the west. This took me over ZZZ5 and into the tfr surrounding the power plant. Because of the current environment with national security, I have tried to be in contact with ATC during as much of my flying time as possible. I called ZZZ1 approach as soon as I thought they would be able to pick me up on radar to advise them of my route and intentions to land at ZZZ. Shortly after contacting them they informed me of my flight into the tfr. The fdc NOTAM which I used for flight planning did not include the tfr that was contained in a later NOTAM. My failure to get the updated fdc NOTAM (that contained the tfr) resulted in my not having all of the information that I needed for the planned flight. Clear sky, unlimited visibility, and a busy ZZZ1 departure resulted in my decision to cancel an IFR flight plan and proceed VFR. The decision to fly VFR from ZZZ2 to ZZZ3 and not contact ZZZ1 departure caused me to navigate without the benefit of the tfr information that ATC had and could of shared with me. The volume of NOTAMS following 11/tue/01 and the frequency with which they are changed is taxing the flight information briefing system and the users of this system. It is particularly confusing when a NOTAM is issued and then subsequently replaced with a similar NOTAM. The user may think they have the current information, but they do not. I need to be more aggressive in obtaining the current NOTAMS that are applicable to both the route of my flts and the area surrounding these routes. If FSS does not offer NOTAM information, I must request it. Furthermore, it is not enough to be aware of the subject matter of an applicable NOTAM, I must also be aware of the specific number of the current NOTAM relative to the subject matter in question. When doing preflight work in advance of a flight I will now record the number of the NOTAM used and confirm with FSS immediately prior to the flight that these are current during the time of my flight. Because of the dynamic nature of NOTAMS, the complexity of NOTAM information, and the multiple sources of information on NOTAMS, I believe the flight training and briefing should be expanded to emphasize using the unique NOTAM identification number when communicating NOTAM information.
Original NASA ASRS Text
Title: AN SMA PLT VIOLATED A TFR INVOLVING A PWR PLANT.
Narrative: ON 11/FRI/01 I ACCEPTED A MISSION TO TRANSPORT AN INDIVIDUAL FROM ZZZ TO ZZZ1 ON THE FOLLOWING MONDAY. I IMMEDIATELY BEGAN THE PREFLT WORK WHICH INCLUDED GATHERING THE INFO ON FDC NOTAM DESCRIBING THE TFRS AROUND PWR PLANTS, MARKING UP MY CHARTS TO CLEARLY IDENTIFY ALL OF THESE TFRS, AND THEN CREATING A ROUTE FROM ZZZ2 TO ZZZ3 AND RETURNING TO ZZZ THAT WOULD AVOID THE TFRS. I USED GRAPHICS PROVIDED ON A WEB SITE TO ASSIST IN PLOTTING THE TFRS. ON SUNDAY, AT APPROX XA00 I CALLED FSS TO GET AN OUTLOOK BRIEFING FOR THE NEXT DAY'S FLTS AND RECEIVED THE WEATHER INFO, BUT NO INFO ON TFR NOTAMS. I FILED IFR FLT PLANS FOR EACH OF THE 3 LEGS I WOULD FLY ON MONDAY. ON MONDAY AT XB30 I CALLED FSS TO GET AN UPDATED BRIEFING, BUT AGAIN RECEIVED NO INFO ON TFR NOTAMS. ON BOTH OF THESE CALLS THE BRIEFER DID NOT OFFER, NOR DID I ASK FOR THE TFR NOTAM. I FLEW THE FIRST TWO LEGS IFR AS FILED BUT WHEN IT WAS TIME TO DEPART ZZZ1 THE ACFT IN FRONT OF ME AND I WERE HELD BY ZZZ1 DEP. WE BOTH DECIDED TO GO VFR AND WERE RELEASED. BECAUSE ZZZ1 DEP WAS BUSY I PROCEEDED N WITHOUT CONTACTING THEM. WHEN I WAS N OF ZZZ1 CLASS B SPACE I TURNED NW TO CLR ZZZ4 CLASS C TO THE W. THIS TOOK ME OVER ZZZ5 AND INTO THE TFR SURROUNDING THE PWR PLANT. BECAUSE OF THE CURRENT ENVIRONMENT WITH NATIONAL SECURITY, I HAVE TRIED TO BE IN CONTACT WITH ATC DURING AS MUCH OF MY FLYING TIME AS POSSIBLE. I CALLED ZZZ1 APCH AS SOON AS I THOUGHT THEY WOULD BE ABLE TO PICK ME UP ON RADAR TO ADVISE THEM OF MY ROUTE AND INTENTIONS TO LAND AT ZZZ. SHORTLY AFTER CONTACTING THEM THEY INFORMED ME OF MY FLT INTO THE TFR. THE FDC NOTAM WHICH I USED FOR FLT PLANNING DID NOT INCLUDE THE TFR THAT WAS CONTAINED IN A LATER NOTAM. MY FAILURE TO GET THE UPDATED FDC NOTAM (THAT CONTAINED THE TFR) RESULTED IN MY NOT HAVING ALL OF THE INFO THAT I NEEDED FOR THE PLANNED FLT. CLR SKY, UNLIMITED VISIBILITY, AND A BUSY ZZZ1 DEP RESULTED IN MY DECISION TO CANCEL AN IFR FLT PLAN AND PROCEED VFR. THE DECISION TO FLY VFR FROM ZZZ2 TO ZZZ3 AND NOT CONTACT ZZZ1 DEP CAUSED ME TO NAVIGATE WITHOUT THE BENEFIT OF THE TFR INFO THAT ATC HAD AND COULD OF SHARED WITH ME. THE VOLUME OF NOTAMS FOLLOWING 11/TUE/01 AND THE FREQ WITH WHICH THEY ARE CHANGED IS TAXING THE FLT INFO BRIEFING SYSTEM AND THE USERS OF THIS SYSTEM. IT IS PARTICULARLY CONFUSING WHEN A NOTAM IS ISSUED AND THEN SUBSEQUENTLY REPLACED WITH A SIMILAR NOTAM. THE USER MAY THINK THEY HAVE THE CURRENT INFO, BUT THEY DO NOT. I NEED TO BE MORE AGGRESSIVE IN OBTAINING THE CURRENT NOTAMS THAT ARE APPLICABLE TO BOTH THE ROUTE OF MY FLTS AND THE AREA SURROUNDING THESE ROUTES. IF FSS DOES NOT OFFER NOTAM INFO, I MUST REQUEST IT. FURTHERMORE, IT IS NOT ENOUGH TO BE AWARE OF THE SUBJECT MATTER OF AN APPLICABLE NOTAM, I MUST ALSO BE AWARE OF THE SPECIFIC NUMBER OF THE CURRENT NOTAM RELATIVE TO THE SUBJECT MATTER IN QUESTION. WHEN DOING PREFLT WORK IN ADVANCE OF A FLT I WILL NOW RECORD THE NUMBER OF THE NOTAM USED AND CONFIRM WITH FSS IMMEDIATELY PRIOR TO THE FLT THAT THESE ARE CURRENT DURING THE TIME OF MY FLT. BECAUSE OF THE DYNAMIC NATURE OF NOTAMS, THE COMPLEXITY OF NOTAM INFO, AND THE MULTIPLE SOURCES OF INFO ON NOTAMS, I BELIEVE THE FLT TRAINING AND BRIEFING SHOULD BE EXPANDED TO EMPHASIZE USING THE UNIQUE NOTAM IDENTIFICATION NUMBER WHEN COMMUNICATING NOTAM INFO.
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.