 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Pilot of R22 helicopter departed jyo within the dc ADIZ without obtaining discreet transponder code. Had received briefing from leesburg FSS, but was incorrectly advised to pick up his discrete code from pct after takeoff.
| Attributes | |
| ACN | 595615 |
| Time | |
| Date | 200310 |
| Day | Sun |
| Local Time Of Day | 1201 To 1800 |
| Place | |
| State Reference | VA |
| Altitude | msl single value : 1000 |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Controlling Facilities | tracon : pct.tracon tower : jyo.tower |
| Operator | general aviation : personal |
| Make Model Name | Robinson R22 |
| Operating Under FAR Part | Part 91 |
| Flight Phase | 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 : 46 flight time total : 119 flight time type : 109 |
| ASRS Report | 595615 |
| Person 2 | |
| Affiliation | government : faa |
| Function | other personnel |
| Events | |
| Anomaly | airspace violation : entry non adherence : far non adherence : published procedure |
| Independent Detector | other controllera |
| Resolutory Action | controller : issued advisory other |
| Consequence | faa : assigned or threatened penalties faa : reviewed incident with flight crew faa : investigated |
| Supplementary | |
| Problem Areas | Airspace Structure Airport Environmental Factor Flight Crew Human Performance FAA |
| Primary Problem | ATC Human Performance |
| Air Traffic Incident | Pilot Deviation |
| Situations | |
| Airspace Structure | special use : dcadiz.othersua |
Narrative:
I called leesburg flight service to file an ADIZ flight plan from leesburg executive to chester company airport. After the flight plan was filed, I asked the briefer for my transponder code. The briefer informed me that after takeoff, potomac approach will give me a squawk code. I contacted potomac approach as soon as possible after takeoff. Potomac approach informed me that flight service should have given me a code. I then turned back and landed at leesburg executive. To contact the office. The person I spoke with at potomac approach listened to the event and contacted leesburg flight service. He said he was sorry about the mix-up, but he had to file the report, because the squawk code is necessary for takeoff.
Original NASA ASRS Text
Title: PLT OF R22 HELI DEPARTED JYO WITHIN THE DC ADIZ WITHOUT OBTAINING DISCREET XPONDER CODE. HAD RECEIVED BRIEFING FROM LEESBURG FSS, BUT WAS INCORRECTLY ADVISED TO PICK UP HIS DISCRETE CODE FROM PCT AFTER TKOF.
Narrative: I CALLED LEESBURG FLT SVC TO FILE AN ADIZ FLT PLAN FROM LEESBURG EXECUTIVE TO CHESTER COMPANY ARPT. AFTER THE FLT PLAN WAS FILED, I ASKED THE BRIEFER FOR MY XPONDER CODE. THE BRIEFER INFORMED ME THAT AFTER TKOF, POTOMAC APCH WILL GIVE ME A SQUAWK CODE. I CONTACTED POTOMAC APCH AS SOON AS POSSIBLE AFTER TKOF. POTOMAC APCH INFORMED ME THAT FLT SVC SHOULD HAVE GIVEN ME A CODE. I THEN TURNED BACK AND LANDED AT LEESBURG EXECUTIVE. TO CONTACT THE OFFICE. THE PERSON I SPOKE WITH AT POTOMAC APCH LISTENED TO THE EVENT AND CONTACTED LEESBURG FLT SVC. HE SAID HE WAS SORRY ABOUT THE MIX-UP, BUT HE HAD TO FILE THE RPT, BECAUSE THE SQUAWK CODE IS NECESSARY FOR TKOF.
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.