37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 634334 |
Time | |
Date | 200410 |
Day | Sat |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | airport : sfb.airport |
State Reference | FL |
Altitude | msl single value : 1500 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tower : sfb.tower |
Operator | general aviation : personal |
Make Model Name | Skyhawk 172/Cutlass 172 |
Operating Under FAR Part | Part 91 |
Flight Phase | climbout : intermediate altitude cruise : level |
Flight Plan | VFR |
Person 1 | |
Affiliation | other |
Function | flight crew : single pilot |
Qualification | pilot : private |
Experience | flight time last 90 days : 19.6 flight time total : 337.5 flight time type : 139.9 |
ASRS Report | 634334 |
Person 2 | |
Affiliation | government : faa |
Function | controller : local |
Events | |
Anomaly | airspace violation : entry non adherence : published procedure non adherence : far non adherence : clearance non adherence other |
Independent Detector | other controllera |
Resolutory Action | controller : issued advisory controller : issued new clearance |
Consequence | faa : reviewed incident with flight crew |
Supplementary | |
Problem Areas | Flight Crew Human Performance Airspace Structure |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
The first indication that there was a problem was when the tower controller brought it to my attention. At that time I was outside of the airspace that I thought I was supposed to avoid. I was then informed that I was not to avoid the airspace between 180 degrees and 220 degrees, but to fly within it. I was still within class D airspace at this time, and on tower frequency. I discovered I had made a serious mistake. After the tower controller's verbal reprimand, and my profuse apology, I then turned on a southerly course, and was further instructed to telephone the tower when I landed at my destination. This was approximately +/-1 hour 45 mins later after closing my flight plan. Request frequency change from tower to get flight following and was granted it. After landing I called the control tower. A gentleman answered and idented himself as 'captain?' I missed getting his last name and did not think to ask him again after I explained the message for my call. He did state to me that the person that I was supposed to talk to had already left for the day and apparently did not feel it was important enough to wait for my call. On the following monday, I called tower again and spoke to control tower supervisor. After explaining to him the purpose of my call, he informed me per our conversation, that he looked at the tower logbook and stated that nothing was filed or logged concerning the tfr incident I had mentioned. He asked me for the aircraft tail number which I gave him. He stated that there was nothing filed or logged concerning that tail number. He further stated that I shouldn't worry about it. I then gave him my full name and both my home and cellular phone numbers if he needed to reach me concerning this matter. This was the first time I have ever flown when a tfr is/has been in effect.
Original NASA ASRS Text
Title: A C182 PLT MISUNDERSTOOD A TFR AIRSPACE DEFINITION AND VIOLATED THE RESTR AIRSPACE.
Narrative: THE FIRST INDICATION THAT THERE WAS A PROB WAS WHEN THE TWR CTLR BROUGHT IT TO MY ATTN. AT THAT TIME I WAS OUTSIDE OF THE AIRSPACE THAT I THOUGHT I WAS SUPPOSED TO AVOID. I WAS THEN INFORMED THAT I WAS NOT TO AVOID THE AIRSPACE BTWN 180 DEGS AND 220 DEGS, BUT TO FLY WITHIN IT. I WAS STILL WITHIN CLASS D AIRSPACE AT THIS TIME, AND ON TWR FREQ. I DISCOVERED I HAD MADE A SERIOUS MISTAKE. AFTER THE TWR CTLR'S VERBAL REPRIMAND, AND MY PROFUSE APOLOGY, I THEN TURNED ON A SOUTHERLY COURSE, AND WAS FURTHER INSTRUCTED TO TELEPHONE THE TWR WHEN I LANDED AT MY DEST. THIS WAS APPROX +/-1 HR 45 MINS LATER AFTER CLOSING MY FLT PLAN. REQUEST FREQ CHANGE FROM TWR TO GET FLT FOLLOWING AND WAS GRANTED IT. AFTER LNDG I CALLED THE CTL TWR. A GENTLEMAN ANSWERED AND IDENTED HIMSELF AS 'CAPT?' I MISSED GETTING HIS LAST NAME AND DID NOT THINK TO ASK HIM AGAIN AFTER I EXPLAINED THE MESSAGE FOR MY CALL. HE DID STATE TO ME THAT THE PERSON THAT I WAS SUPPOSED TO TALK TO HAD ALREADY LEFT FOR THE DAY AND APPARENTLY DID NOT FEEL IT WAS IMPORTANT ENOUGH TO WAIT FOR MY CALL. ON THE FOLLOWING MONDAY, I CALLED TWR AGAIN AND SPOKE TO CTL TWR SUPVR. AFTER EXPLAINING TO HIM THE PURPOSE OF MY CALL, HE INFORMED ME PER OUR CONVERSATION, THAT HE LOOKED AT THE TWR LOGBOOK AND STATED THAT NOTHING WAS FILED OR LOGGED CONCERNING THE TFR INCIDENT I HAD MENTIONED. HE ASKED ME FOR THE ACFT TAIL NUMBER WHICH I GAVE HIM. HE STATED THAT THERE WAS NOTHING FILED OR LOGGED CONCERNING THAT TAIL NUMBER. HE FURTHER STATED THAT I SHOULDN'T WORRY ABOUT IT. I THEN GAVE HIM MY FULL NAME AND BOTH MY HOME AND CELLULAR PHONE NUMBERS IF HE NEEDED TO REACH ME CONCERNING THIS MATTER. THIS WAS THE FIRST TIME I HAVE EVER FLOWN WHEN A TFR IS/HAS BEEN IN EFFECT.
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.