37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 576176 |
Time | |
Date | 200303 |
Day | Mon |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | airport : fdk.airport |
State Reference | MD |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tracon : pct.tracon |
Operator | general aviation : corporate |
Make Model Name | Citation III, VI, VII |
Operating Under FAR Part | Part 91 |
Flight Phase | climbout : takeoff climbout : initial |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : corporate |
Function | flight crew : first officer |
Qualification | pilot : multi engine pilot : atp |
Experience | flight time last 90 days : 100 flight time total : 6700 flight time type : 150 |
ASRS Report | 576176 |
Person 2 | |
Affiliation | company : corporate |
Function | flight crew : captain oversight : pic |
Events | |
Anomaly | airspace violation : entry non adherence : published procedure non adherence : far non adherence other |
Independent Detector | other controllera |
Resolutory Action | none taken : detected after the fact |
Consequence | Other |
Supplementary | |
Problem Areas | FAA Flight Crew Human Performance Environmental Factor ATC Human Performance Airspace Structure Chart Or Publication |
Primary Problem | FAA |
Air Traffic Incident | Pilot Deviation |
Situations | |
Airspace Structure | special use : dcadiz.othersua |
Narrative:
The captain and I flew our company citation vii from pvd to fdk to meet an individual for the purpose of testing the aircraft. Fdk is an uncontrolled field, and after we arrived we met the individual we were to pick up. The captain went inside and filed a round robin IFR flight plan to accomplish our mission. We went back out to the airplane to start up and pick up our IFR clearance. This is where our troubles began. Even though fdk is uncontrolled it has a clearance frequency to use for picking up IFR flight plans. Even though the captain tried to contact clearance about 5 to 8 times, they did not answer. As I taxied out to runway 23, the captain tried several times and on different frequency's (clearance del and approach departure ctrl). But no one answered. (These frequency's were verified to be good frequency's by bwi approach on the way into fdk on our first leg). Since we were trying and no one was answering, we figured we might be in a dead spot on the airport and decided a reasonable thing to do was to takeoff VFR (weather was not at all an issue) and contact bwi approach immediately after takeoff. We did this, but still no one was answering and we tried several times. Finally they answered us back, we picked up an IFR and shortly thereafter we were told that when we return to fdk, to call a certain phone number because of an ADIZ violation. The captain and I looked at each other in disbelief 'what ADIZ?' there was nothing on the VFR sectional chart except P40 and we know we didn't go near that, and there was nothing told to me about an ADIZ, when checking the NOTAMS by the FSS briefer on the phone back in providence before we left. So we were truly caught off guard and completely by surprise. When we returned to fdk, we were met by 3 us customs agents and brought upstairs into a room where they explained to us about an ADIZ, that had been put in place sometime since sep/tue/01. This airspace extends from the surface to 1800 ft all the way around the washington and dulles class B and even extends beyond the lateral limits of the class B and even covers fdk. So we were in violation as soon as we rotated and wheels up to, add to the mess, we also managed to clip the edge of the dulles class B while we were maneuvering and trying to raise someone on the radio. While I will admit that we should have done a better job of our positional awareness with regard to the class B, I find it hard to accept fault for the ADIZ violation since I asked about it in the WX briefing and was not given that information, the ADIZ was not shown on the sectional chart and the ATC controller told us that he heard all our calls to him on the ground and in the air, but was too busy on other frequency's to answer us back. Ps: the customs officials were very nice and told us this happens 5 to 6 times per day.
Original NASA ASRS Text
Title: FLC OF C650 PENETRATED DC ADIZ WHILE ATTEMPTING TO CONTACT PCT TRACON FOR IFR CLRNC.
Narrative: THE CAPT AND I FLEW OUR COMPANY CITATION VII FROM PVD TO FDK TO MEET AN INDIVIDUAL FOR THE PURPOSE OF TESTING THE ACFT. FDK IS AN UNCTLED FIELD, AND AFTER WE ARRIVED WE MET THE INDIVIDUAL WE WERE TO PICK UP. THE CAPT WENT INSIDE AND FILED A ROUND ROBIN IFR FLT PLAN TO ACCOMPLISH OUR MISSION. WE WENT BACK OUT TO THE AIRPLANE TO START UP AND PICK UP OUR IFR CLRNC. THIS IS WHERE OUR TROUBLES BEGAN. EVEN THOUGH FDK IS UNCTLED IT HAS A CLRNC FREQ TO USE FOR PICKING UP IFR FLT PLANS. EVEN THOUGH THE CAPT TRIED TO CONTACT CLRNC ABOUT 5 TO 8 TIMES, THEY DID NOT ANSWER. AS I TAXIED OUT TO RWY 23, THE CAPT TRIED SEVERAL TIMES AND ON DIFFERENT FREQ'S (CLRNC DEL AND APCH DEP CTRL). BUT NO ONE ANSWERED. (THESE FREQ'S WERE VERIFIED TO BE GOOD FREQ'S BY BWI APCH ON THE WAY INTO FDK ON OUR FIRST LEG). SINCE WE WERE TRYING AND NO ONE WAS ANSWERING, WE FIGURED WE MIGHT BE IN A DEAD SPOT ON THE ARPT AND DECIDED A REASONABLE THING TO DO WAS TO TAKEOFF VFR (WEATHER WAS NOT AT ALL AN ISSUE) AND CONTACT BWI APCH IMMEDIATELY AFTER TAKEOFF. WE DID THIS, BUT STILL NO ONE WAS ANSWERING AND WE TRIED SEVERAL TIMES. FINALLY THEY ANSWERED US BACK, WE PICKED UP AN IFR AND SHORTLY THEREAFTER WE WERE TOLD THAT WHEN WE RETURN TO FDK, TO CALL A CERTAIN PHONE NUMBER BECAUSE OF AN ADIZ VIOLATION. THE CAPT AND I LOOKED AT EACH OTHER IN DISBELIEF 'WHAT ADIZ?' THERE WAS NOTHING ON THE VFR SECTIONAL CHART EXCEPT P40 AND WE KNOW WE DIDN'T GO NEAR THAT, AND THERE WAS NOTHING TOLD TO ME ABOUT AN ADIZ, WHEN CHKING THE NOTAMS BY THE FSS BRIEFER ON THE PHONE BACK IN PROVIDENCE BEFORE WE LEFT. SO WE WERE TRULY CAUGHT OFF GUARD AND COMPLETELY BY SURPRISE. WHEN WE RETURNED TO FDK, WE WERE MET BY 3 US CUSTOMS AGENTS AND BROUGHT UPSTAIRS INTO A ROOM WHERE THEY EXPLAINED TO US ABOUT AN ADIZ, THAT HAD BEEN PUT IN PLACE SOMETIME SINCE SEP/TUE/01. THIS AIRSPACE EXTENDS FROM THE SURFACE TO 1800 FT ALL THE WAY AROUND THE WASHINGTON AND DULLES CLASS B AND EVEN EXTENDS BEYOND THE LATERAL LIMITS OF THE CLASS B AND EVEN COVERS FDK. SO WE WERE IN VIOLATION AS SOON AS WE ROTATED AND WHEELS UP TO, ADD TO THE MESS, WE ALSO MANAGED TO CLIP THE EDGE OF THE DULLES CLASS B WHILE WE WERE MANEUVERING AND TRYING TO RAISE SOMEONE ON THE RADIO. WHILE I WILL ADMIT THAT WE SHOULD HAVE DONE A BETTER JOB OF OUR POSITIONAL AWARENESS WITH REGARD TO THE CLASS B, I FIND IT HARD TO ACCEPT FAULT FOR THE ADIZ VIOLATION SINCE I ASKED ABOUT IT IN THE WX BRIEFING AND WAS NOT GIVEN THAT INFO, THE ADIZ WAS NOT SHOWN ON THE SECTIONAL CHART AND THE ATC CTLR TOLD US THAT HE HEARD ALL OUR CALLS TO HIM ON THE GND AND IN THE AIR, BUT WAS TOO BUSY ON OTHER FREQ'S TO ANSWER US BACK. PS: THE CUSTOMS OFFICIALS WERE VERY NICE AND TOLD US THIS HAPPENS 5 TO 6 TIMES PER DAY.
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.