37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 611308 |
Time | |
Date | 200403 |
Day | Sun |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | airport : 2w5.airport |
State Reference | MD |
Altitude | msl single value : 1200 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tracon : pct.tracon |
Operator | general aviation : personal |
Make Model Name | Cessna 180 Skywagon |
Operating Under FAR Part | Part 91 |
Navigation In Use | other vortac |
Flight Phase | climbout : initial climbout : intermediate altitude |
Route In Use | departure : vfr |
Flight Plan | VFR |
Person 1 | |
Affiliation | other |
Function | flight crew : single pilot |
Qualification | pilot : private |
Experience | flight time last 90 days : 8 flight time total : 1400 flight time type : 1000 |
ASRS Report | 611308 |
Person 2 | |
Function | observation : passenger |
Events | |
Anomaly | airspace violation : entry altitude deviation : overshoot non adherence : far non adherence : clearance non adherence : published procedure |
Independent Detector | other flight crewa |
Resolutory Action | flight crew : landed as precaution flight crew : exited penetrated airspace flight crew : diverted to another airport other |
Consequence | faa : reviewed incident with flight crew |
Supplementary | |
Problem Areas | Flight Crew Human Performance Aircraft |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
Pilot prepared to fly a C170 purchased by a friend from its seller at 2w5 (maryland airport). The airport is under the washington, dc, ADIZ, so he downloaded the departure procedure from pilot web site. In accordance with this information, he called the leesburg FSS and filed his ADIZ penetration flight plan. He then called potomac approach and received his discrete transponder code and departure frequency. The aircraft was then fueled and preflted. Pilot has over 900 hours in his own aircraft, a C170, but all airplanes have various items that are unique to that aircraft. The aircraft that pilot was retrieving, under part 91, has narco radios. The C170 he regularly flies has king radios. In addition, the switch panel for the intercom and headsets, which were installed by the previous owner, were not well marked so the owner briefed the pilot, and the new owner who was accompanying pilot, together. After the engine run-up, pilot confirmed the radio frequencys and did a radio check with the FBO on the CTAF. Upon departure, pilot began to climb on course for the brooke VOR, which was the filed route. Once he reached 800 ft MSL, pilot attempted to call potomac but did not receive a response to his call. Pilot continued to call, when able, between other traffic xmissions until he passed through approximately 1500 ft. The controller at potomac who provided the discrete squawk code earlier had advised pilot that potomac should be able to talk to pilots departing aircraft quickly once in the air off 2w5, maybe only at 400-500 ft MSL. When pilot's attempts to contact potomac were not answered, pilot became very concerned that he may have a radio failure since he could not establish 2-WAY radio contact. The newly-purchased aircraft had only 1 communication radio, so switching radios was not an option. Recognizing that he and his companion were in highly sensitive airspace, pilot determined that the most prudent thing to do was to turn back immediately and get the aircraft on the ground. Pilot was only 5-6 mi out at this time and was able to return quickly. Upon entry into the pattern, pilot was unable to raise anyone on unicom, which he had done previously during the radio check before departure. Once on the ground, as pilot taxied back to the FBO, the new owner of the aircraft began to troubleshoot the problem. The new owner and copilot found that one of the small switches on the intercom panel was not in the position that it should have been in. The problem was rectified, and the aircraft was again able to transmit to the FBO. Pilot shut down the engine on the ramp and immediately went into the office and called potomac. The line was busy for a short time, but when pilot got through to potomac, pilot explained to the controller what had happened. The potomac controller stated, 'ok, I'll let them know.' pilot also told the controller that the problem had been fixed, and that pilot would like to depart again. The controller indicated that departure would be fine, but that since pilot had 'tanked up on the system, but dropped out,' pilot would need to go through the entire departure filing sequence once again. Pilot called leesburg FSS for a new ADIZ flight plan. When pilot explained what had happened the first time, as well as pilot's actions in response to the radio difficulty, the briefer told pilot that pilot had done the right thing. With the new flight plan filed, pilot called potomac again and received the new discrete transponder code. On the second departure attempt, pilot waited until he was approximately 1000 ft MSL before making his first call. Again, he received no response. Pilot called again, and this time the controller responded, 'do I hear '1234X calling?' pilot was actually flying '1234Y' and pilot thought that the controller might be trying to reach pilot, but that perhaps controller had misunderstood pilot's transmission and identify. The frequency was very busy, and pilot did not want to step on someone else's transmission. Pilot waited a short time and no one answered the controller, so pilot assumed that controller was calling for pilot's '34Y.' pilot answered with 'cessna 1234Y climbing out of maryland 2w5 with ADIZ flight plan on file, squawking XXXX,' and controller responded with '34Y we show you on course.' later came a frequency change and then release as pilot cleared the ADIZ boundary.
Original NASA ASRS Text
Title: A C170 SINGLE PLT INADVERTENTLY VIOLATED THE DC ADIZ, AFTER EXCELLENT PREDEP PLANNING, BRIEFING AND PREFLTING.
Narrative: PLT PREPARED TO FLY A C170 PURCHASED BY A FRIEND FROM ITS SELLER AT 2W5 (MARYLAND ARPT). THE ARPT IS UNDER THE WASHINGTON, DC, ADIZ, SO HE DOWNLOADED THE DEP PROC FROM PLT WEB SITE. IN ACCORDANCE WITH THIS INFO, HE CALLED THE LEESBURG FSS AND FILED HIS ADIZ PENETRATION FLT PLAN. HE THEN CALLED POTOMAC APCH AND RECEIVED HIS DISCRETE XPONDER CODE AND DEP FREQ. THE ACFT WAS THEN FUELED AND PREFLTED. PLT HAS OVER 900 HRS IN HIS OWN ACFT, A C170, BUT ALL AIRPLANES HAVE VARIOUS ITEMS THAT ARE UNIQUE TO THAT ACFT. THE ACFT THAT PLT WAS RETRIEVING, UNDER PART 91, HAS NARCO RADIOS. THE C170 HE REGULARLY FLIES HAS KING RADIOS. IN ADDITION, THE SWITCH PANEL FOR THE INTERCOM AND HEADSETS, WHICH WERE INSTALLED BY THE PREVIOUS OWNER, WERE NOT WELL MARKED SO THE OWNER BRIEFED THE PLT, AND THE NEW OWNER WHO WAS ACCOMPANYING PLT, TOGETHER. AFTER THE ENG RUN-UP, PLT CONFIRMED THE RADIO FREQS AND DID A RADIO CHK WITH THE FBO ON THE CTAF. UPON DEP, PLT BEGAN TO CLB ON COURSE FOR THE BROOKE VOR, WHICH WAS THE FILED RTE. ONCE HE REACHED 800 FT MSL, PLT ATTEMPTED TO CALL POTOMAC BUT DID NOT RECEIVE A RESPONSE TO HIS CALL. PLT CONTINUED TO CALL, WHEN ABLE, BTWN OTHER TFC XMISSIONS UNTIL HE PASSED THROUGH APPROX 1500 FT. THE CTLR AT POTOMAC WHO PROVIDED THE DISCRETE SQUAWK CODE EARLIER HAD ADVISED PLT THAT POTOMAC SHOULD BE ABLE TO TALK TO PLTS DEPARTING ACFT QUICKLY ONCE IN THE AIR OFF 2W5, MAYBE ONLY AT 400-500 FT MSL. WHEN PLT'S ATTEMPTS TO CONTACT POTOMAC WERE NOT ANSWERED, PLT BECAME VERY CONCERNED THAT HE MAY HAVE A RADIO FAILURE SINCE HE COULD NOT ESTABLISH 2-WAY RADIO CONTACT. THE NEWLY-PURCHASED ACFT HAD ONLY 1 COM RADIO, SO SWITCHING RADIOS WAS NOT AN OPTION. RECOGNIZING THAT HE AND HIS COMPANION WERE IN HIGHLY SENSITIVE AIRSPACE, PLT DETERMINED THAT THE MOST PRUDENT THING TO DO WAS TO TURN BACK IMMEDIATELY AND GET THE ACFT ON THE GND. PLT WAS ONLY 5-6 MI OUT AT THIS TIME AND WAS ABLE TO RETURN QUICKLY. UPON ENTRY INTO THE PATTERN, PLT WAS UNABLE TO RAISE ANYONE ON UNICOM, WHICH HE HAD DONE PREVIOUSLY DURING THE RADIO CHK BEFORE DEP. ONCE ON THE GND, AS PLT TAXIED BACK TO THE FBO, THE NEW OWNER OF THE ACFT BEGAN TO TROUBLESHOOT THE PROB. THE NEW OWNER AND COPLT FOUND THAT ONE OF THE SMALL SWITCHES ON THE INTERCOM PANEL WAS NOT IN THE POS THAT IT SHOULD HAVE BEEN IN. THE PROB WAS RECTIFIED, AND THE ACFT WAS AGAIN ABLE TO XMIT TO THE FBO. PLT SHUT DOWN THE ENG ON THE RAMP AND IMMEDIATELY WENT INTO THE OFFICE AND CALLED POTOMAC. THE LINE WAS BUSY FOR A SHORT TIME, BUT WHEN PLT GOT THROUGH TO POTOMAC, PLT EXPLAINED TO THE CTLR WHAT HAD HAPPENED. THE POTOMAC CTLR STATED, 'OK, I'LL LET THEM KNOW.' PLT ALSO TOLD THE CTLR THAT THE PROB HAD BEEN FIXED, AND THAT PLT WOULD LIKE TO DEPART AGAIN. THE CTLR INDICATED THAT DEP WOULD BE FINE, BUT THAT SINCE PLT HAD 'TANKED UP ON THE SYS, BUT DROPPED OUT,' PLT WOULD NEED TO GO THROUGH THE ENTIRE DEP FILING SEQUENCE ONCE AGAIN. PLT CALLED LEESBURG FSS FOR A NEW ADIZ FLT PLAN. WHEN PLT EXPLAINED WHAT HAD HAPPENED THE FIRST TIME, AS WELL AS PLT'S ACTIONS IN RESPONSE TO THE RADIO DIFFICULTY, THE BRIEFER TOLD PLT THAT PLT HAD DONE THE RIGHT THING. WITH THE NEW FLT PLAN FILED, PLT CALLED POTOMAC AGAIN AND RECEIVED THE NEW DISCRETE XPONDER CODE. ON THE SECOND DEP ATTEMPT, PLT WAITED UNTIL HE WAS APPROX 1000 FT MSL BEFORE MAKING HIS FIRST CALL. AGAIN, HE RECEIVED NO RESPONSE. PLT CALLED AGAIN, AND THIS TIME THE CTLR RESPONDED, 'DO I HEAR '1234X CALLING?' PLT WAS ACTUALLY FLYING '1234Y' AND PLT THOUGHT THAT THE CTLR MIGHT BE TRYING TO REACH PLT, BUT THAT PERHAPS CTLR HAD MISUNDERSTOOD PLT'S XMISSION AND IDENT. THE FREQ WAS VERY BUSY, AND PLT DID NOT WANT TO STEP ON SOMEONE ELSE'S XMISSION. PLT WAITED A SHORT TIME AND NO ONE ANSWERED THE CTLR, SO PLT ASSUMED THAT CTLR WAS CALLING FOR PLT'S '34Y.' PLT ANSWERED WITH 'CESSNA 1234Y CLBING OUT OF MARYLAND 2W5 WITH ADIZ FLT PLAN ON FILE, SQUAWKING XXXX,' AND CTLR RESPONDED WITH '34Y WE SHOW YOU ON COURSE.' LATER CAME A FREQ CHANGE AND THEN RELEASE AS PLT CLRED THE ADIZ BOUNDARY.
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.