 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
C208 pilot violates tfr between syi and bna airports. Pilot alleges transponder code changed at direction of ZME.
| Attributes | |
| ACN | 618913 |
| Time | |
| Date | 200405 |
| Day | Thu |
| Local Time Of Day | 1201 To 1800 |
| Place | |
| Locale Reference | airport : syi.airport |
| State Reference | TN |
| Altitude | msl single value : 3000 |
| Environment | |
| Flight Conditions | Mixed |
| Light | Daylight |
| Aircraft 1 | |
| Controlling Facilities | tracon : mem.tracon |
| Operator | common carrier : charter |
| Make Model Name | Cessna Single Piston Undifferentiated or Other Model |
| Operating Under FAR Part | Part 91 |
| Navigation In Use | other |
| Flight Phase | descent : approach |
| Route In Use | approach : traffic pattern |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | company : charter |
| Function | flight crew : single pilot |
| Qualification | pilot : cfi pilot : multi engine pilot : instrument pilot : commercial |
| Experience | controller military : 5 controller non radar : 5 controller radar : 5 controller supervisory : 5 flight time last 90 days : 300 flight time total : 2000 flight time type : 375 |
| ASRS Report | 618913 |
| Person 2 | |
| Affiliation | government : faa |
| Function | controller : approach |
| Events | |
| Anomaly | airspace violation : entry inflight encounter : weather non adherence : far non adherence : published procedure |
| Independent Detector | atc equipment other atc equipment : radar other controllera |
| Resolutory Action | none taken : detected after the fact |
| Consequence | faa : investigated faa : reviewed incident with flight crew |
| Supplementary | |
| Problem Areas | Flight Crew Human Performance ATC Human Performance |
| Primary Problem | Flight Crew Human Performance |
| Air Traffic Incident | Pilot Deviation |
Narrative:
I had a charter flight for the company I work for. About over nashville, I asked the approach controller for lower. He approved the descent from 6000 ft to 4000 ft. I was then given a vector of 180 degrees to stay clear of a tfr for 20 mi or so, then back on course. I then asked for 3000 ft so that I could get into VFR conditions. At this time, I was about 25 mi out from shelbyville and was told by nashville to contact memphis for lower. I contacted memphis and advised them of my request. They approved me to 3000 ft and advised me that there was an IFR departure off of shelbyville and it could be as much as 12 mins till I could get in. I was now about 15 mi from the airport in VFR conditions. I advised him that I could just proceed in VFR to help the situation. He told me to squawk VFR and frequency change approved. I continued inbound and called memphis back to check on the traffic, which was not a factor at this time. When I landed, I had a note from nashville to call them. I called and talked to the supervisor. He advised me that I busted a tfr and was being violated. I then unloaded my cargo and took care of my work before calling him back to straighten out the mess. When I called back, he told me that the problem was that I had a VFR code in the area to protect the president. If I had kept my IFR code, there would not have been a problem. Shelbyville was just outside of the protected area, but while inbound, I must have clipped the tfr. I explained to the nashville controller that the memphis controller told me to squawk VFR and he said that they were going to check the tapes. I think that this problem could have been avoided if the memphis controller had advised me of the tfr, or at least told me that I could not cancel until I was clear of the area. I was never told the exact location of the tfr. If the controllers saw me heading in that direction, they should have stepped in and turned me.
Original NASA ASRS Text
Title: C208 PLT VIOLATES TFR BTWN SYI AND BNA ARPTS. PLT ALLEGES XPONDER CODE CHANGED AT DIRECTION OF ZME.
Narrative: I HAD A CHARTER FLT FOR THE COMPANY I WORK FOR. ABOUT OVER NASHVILLE, I ASKED THE APCH CTLR FOR LOWER. HE APPROVED THE DSCNT FROM 6000 FT TO 4000 FT. I WAS THEN GIVEN A VECTOR OF 180 DEGS TO STAY CLR OF A TFR FOR 20 MI OR SO, THEN BACK ON COURSE. I THEN ASKED FOR 3000 FT SO THAT I COULD GET INTO VFR CONDITIONS. AT THIS TIME, I WAS ABOUT 25 MI OUT FROM SHELBYVILLE AND WAS TOLD BY NASHVILLE TO CONTACT MEMPHIS FOR LOWER. I CONTACTED MEMPHIS AND ADVISED THEM OF MY REQUEST. THEY APPROVED ME TO 3000 FT AND ADVISED ME THAT THERE WAS AN IFR DEP OFF OF SHELBYVILLE AND IT COULD BE AS MUCH AS 12 MINS TILL I COULD GET IN. I WAS NOW ABOUT 15 MI FROM THE ARPT IN VFR CONDITIONS. I ADVISED HIM THAT I COULD JUST PROCEED IN VFR TO HELP THE SIT. HE TOLD ME TO SQUAWK VFR AND FREQ CHANGE APPROVED. I CONTINUED INBOUND AND CALLED MEMPHIS BACK TO CHK ON THE TFC, WHICH WAS NOT A FACTOR AT THIS TIME. WHEN I LANDED, I HAD A NOTE FROM NASHVILLE TO CALL THEM. I CALLED AND TALKED TO THE SUPVR. HE ADVISED ME THAT I BUSTED A TFR AND WAS BEING VIOLATED. I THEN UNLOADED MY CARGO AND TOOK CARE OF MY WORK BEFORE CALLING HIM BACK TO STRAIGHTEN OUT THE MESS. WHEN I CALLED BACK, HE TOLD ME THAT THE PROB WAS THAT I HAD A VFR CODE IN THE AREA TO PROTECT THE PRESIDENT. IF I HAD KEPT MY IFR CODE, THERE WOULD NOT HAVE BEEN A PROB. SHELBYVILLE WAS JUST OUTSIDE OF THE PROTECTED AREA, BUT WHILE INBOUND, I MUST HAVE CLIPPED THE TFR. I EXPLAINED TO THE NASHVILLE CTLR THAT THE MEMPHIS CTLR TOLD ME TO SQUAWK VFR AND HE SAID THAT THEY WERE GOING TO CHK THE TAPES. I THINK THAT THIS PROB COULD HAVE BEEN AVOIDED IF THE MEMPHIS CTLR HAD ADVISED ME OF THE TFR, OR AT LEAST TOLD ME THAT I COULD NOT CANCEL UNTIL I WAS CLR OF THE AREA. I WAS NEVER TOLD THE EXACT LOCATION OF THE TFR. IF THE CTLRS SAW ME HDG IN THAT DIRECTION, THEY SHOULD HAVE STEPPED IN AND TURNED ME.
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.