37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 575626 |
Time | |
Date | 200303 |
Day | Sat |
Local Time Of Day | 0601 To 1200 |
Place | |
Locale Reference | intersection : cladd |
State Reference | DC |
Altitude | msl single value : 3700 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tracon : pct.tracon |
Make Model Name | PA-44 Seminole Turbo Seminole |
Operating Under FAR Part | Part 91 |
Flight Phase | descent : approach |
Flight Plan | None |
Person 1 | |
Affiliation | other |
Function | flight crew : single pilot |
Qualification | pilot : instrument pilot : commercial pilot : cfi pilot : multi engine |
Experience | flight time last 90 days : 30 flight time total : 948 flight time type : 124 |
ASRS Report | 575626 |
Person 2 | |
Affiliation | other |
Function | observation : passenger other personnel other |
Experience | flight time last 90 days : 173 flight time total : 4669 flight time type : 59 |
ASRS Report | 576168 |
Events | |
Anomaly | airspace violation : entry non adherence : published procedure non adherence : far |
Independent Detector | atc equipment other atc equipment : radar other controllera |
Resolutory Action | controller : issued alert flight crew : exited penetrated airspace other |
Consequence | faa : assigned or threatened penalties faa : reviewed incident with flight crew faa : investigated |
Supplementary | |
Problem Areas | Flight Crew Human Performance Airspace Structure Chart Or Publication |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
I and a safety pilot departed jyo to do practice ILS's at okv. We followed ADIZ procedure to depart jyo by contacting pct approach and obtaining our discrete VFR transponder code in order to take off and fly west through the ADIZ towards okv (okv is well out of the ADIZ). After takeoff, we followed ATC's instructions, then ATC confirmed we had left the ADIZ and told us 'frequency change approved.' we then entered okv's unicom in order to give traffic advisories as we did our practice ILS's. My safety pilot gave me vectors in order to join the localizer outbound to do a procedure turn to cladd intersection, which I did by performing a teardrop entry. My safety pilot had given me an approach briefing of the ILS 32 plate, then handed me the plate, as we work as a 'crew.' after performing the procedure turn and about halfway to the da, unicom called to ask us if we had been to upperville (a private airport). We said we had been in the vicinity, but not at the airport. At da we did a missed approach to come back and do a second procedure turn to a second ILS. Shortly after leaving cladd inbound, unicom called again, confirmed our tail number, and said we had to land to make a land line call. We landed as soon as we could and were told by the unicom operator that we were to call pct TRACON. I spoke to a supervisor. He said someone from the FAA would be calling me. My safety pilot said that the supervisor thought we had entered the ADIZ. We flew back to jyo per ADIZ procedures without incident. When I analyzed the situation, I found that we had probably entered the ADIZ by half to 1 mile while performing the course reversal during the procedure turn. I guess that turning to the parallel entry heading, then doing a standard rate turn inbound all contributed to going beyond 5 NM (upperville airport is about half to 1 mile inside the ADIZ). Contributing factors were lack of pictorial depiction of how okv ILS approach/intersection look in proximity to class B/ADIZ boundary. We had VFR terminal charts on board, but we hadn't measured the NM's for the procedure turn outbound. Another contributing factor is that I was not in the mindset of all the ramifications of flying near the ADIZ -- this was the first time I'd flown since the ADIZ was created here. I had done the okv ILS many times before the ADIZ, and although the procedure turn can take you to the class B boundary, it was never a factor, since the class B floor is 4500 ft in that area, and the procedure turn was done well below that altitude. Solution: if flying anywhere near the ADIZ boundaries, monitor on #2 VOR on armel VOR (which, in that area (western) defines the class B boundary), at 20 DME, which will define the ADIZ as well. Also, pre-planning would have helped (ie measuring precisely the distances needed to do the procedure turn at 'X' ground speed) supplemental information from acn 576168: the only corrective action to avoid this situation is better flight planning. With airspace changing daily it's just not possible to simply go out and do some approachs anymore. Every step of the way has to be preplanned.
Original NASA ASRS Text
Title: PA44 PLT TRAINING WITH A SAFETY PLT ARE DIRECTED TO LAND AT OKV BY PCT TO BE INFORMED OF DC ADIZ VIOLATION AFTER CONDUCTING PRACTICE ILS APCHS.
Narrative: I AND A SAFETY PLT DEPARTED JYO TO DO PRACTICE ILS'S AT OKV. WE FOLLOWED ADIZ PROC TO DEPART JYO BY CONTACTING PCT APCH AND OBTAINING OUR DISCRETE VFR XPONDER CODE IN ORDER TO TAKE OFF AND FLY W THROUGH THE ADIZ TOWARDS OKV (OKV IS WELL OUT OF THE ADIZ). AFTER TAKEOFF, WE FOLLOWED ATC'S INSTRUCTIONS, THEN ATC CONFIRMED WE HAD LEFT THE ADIZ AND TOLD US 'FREQUENCY CHANGE APPROVED.' WE THEN ENTERED OKV'S UNICOM IN ORDER TO GIVE TFC ADVISORIES AS WE DID OUR PRACTICE ILS'S. MY SAFETY PLT GAVE ME VECTORS IN ORDER TO JOIN THE LOCALIZER OUTBOUND TO DO A PROC TURN TO CLADD INTXN, WHICH I DID BY PERFORMING A TEARDROP ENTRY. MY SAFETY PLT HAD GIVEN ME AN APCH BRIEFING OF THE ILS 32 PLATE, THEN HANDED ME THE PLATE, AS WE WORK AS A 'CREW.' AFTER PERFORMING THE PROC TURN AND ABOUT HALFWAY TO THE DA, UNICOM CALLED TO ASK US IF WE HAD BEEN TO UPPERVILLE (A PRIVATE ARPT). WE SAID WE HAD BEEN IN THE VICINITY, BUT NOT AT THE ARPT. AT DA WE DID A MISSED APCH TO COME BACK AND DO A SECOND PROC TURN TO A SECOND ILS. SHORTLY AFTER LEAVING CLADD INBOUND, UNICOM CALLED AGAIN, CONFIRMED OUR TAIL NUMBER, AND SAID WE HAD TO LAND TO MAKE A LAND LINE CALL. WE LANDED AS SOON AS WE COULD AND WERE TOLD BY THE UNICOM OPERATOR THAT WE WERE TO CALL PCT TRACON. I SPOKE TO A SUPVR. HE SAID SOMEONE FROM THE FAA WOULD BE CALLING ME. MY SAFETY PLT SAID THAT THE SUPVR THOUGHT WE HAD ENTERED THE ADIZ. WE FLEW BACK TO JYO PER ADIZ PROCS WITHOUT INCIDENT. WHEN I ANALYZED THE SIT, I FOUND THAT WE HAD PROBABLY ENTERED THE ADIZ BY HALF TO 1 MILE WHILE PERFORMING THE COURSE REVERSAL DURING THE PROC TURN. I GUESS THAT TURNING TO THE PARALLEL ENTRY HDG, THEN DOING A STANDARD RATE TURN INBOUND ALL CONTRIBUTED TO GOING BEYOND 5 NM (UPPERVILLE ARPT IS ABOUT HALF TO 1 MILE INSIDE THE ADIZ). CONTRIBUTING FACTORS WERE LACK OF PICTORIAL DEPICTION OF HOW OKV ILS APCH/INTXN LOOK IN PROXIMITY TO CLASS B/ADIZ BOUNDARY. WE HAD VFR TERMINAL CHARTS ON BOARD, BUT WE HADN'T MEASURED THE NM'S FOR THE PROC TURN OUTBOUND. ANOTHER CONTRIBUTING FACTOR IS THAT I WAS NOT IN THE MINDSET OF ALL THE RAMIFICATIONS OF FLYING NEAR THE ADIZ -- THIS WAS THE FIRST TIME I'D FLOWN SINCE THE ADIZ WAS CREATED HERE. I HAD DONE THE OKV ILS MANY TIMES BEFORE THE ADIZ, AND ALTHOUGH THE PROC TURN CAN TAKE YOU TO THE CLASS B BOUNDARY, IT WAS NEVER A FACTOR, SINCE THE CLASS B FLOOR IS 4500 FT IN THAT AREA, AND THE PROC TURN WAS DONE WELL BELOW THAT ALT. SOLUTION: IF FLYING ANYWHERE NEAR THE ADIZ BOUNDARIES, MONITOR ON #2 VOR ON ARMEL VOR (WHICH, IN THAT AREA (WESTERN) DEFINES THE CLASS B BOUNDARY), AT 20 DME, WHICH WILL DEFINE THE ADIZ AS WELL. ALSO, PRE-PLANNING WOULD HAVE HELPED (IE MEASURING PRECISELY THE DISTANCES NEEDED TO DO THE PROC TURN AT 'X' GND SPEED) SUPPLEMENTAL INFO FROM ACN 576168: THE ONLY CORRECTIVE ACTION TO AVOID THIS SIT IS BETTER FLT PLANNING. WITH AIRSPACE CHANGING DAILY IT'S JUST NOT POSSIBLE TO SIMPLY GO OUT AND DO SOME APCHS ANYMORE. EVERY STEP OF THE WAY HAS TO BE PREPLANNED.
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.