37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 619160 |
Time | |
Date | 200405 |
Day | Sat |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | airport : anp.airport |
State Reference | MD |
Altitude | msl single value : 1000 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tracon : pct.tracon |
Operator | general aviation : personal |
Make Model Name | Skyhawk 172/Cutlass 172 |
Operating Under FAR Part | Part 91 |
Flight Phase | climbout : intermediate altitude |
Flight Plan | None |
Person 1 | |
Affiliation | government : faa |
Function | controller : supervisor |
Qualification | pilot : multi engine pilot : atp |
Experience | flight time last 90 days : 95 flight time total : 12500 flight time type : 400 |
ASRS Report | 619160 |
Events | |
Anomaly | airspace violation : entry non adherence : published procedure non adherence : far |
Independent Detector | atc equipment other atc equipment : radar other controllera |
Resolutory Action | none taken : detected after the fact |
Consequence | faa : reviewed incident with flight crew |
Supplementary | |
Problem Areas | Airspace Structure Flight Crew Human Performance |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
On may/sat/04, at approximately XA30L, I departed anp, (lee-annapolis, md) in a C172, in VFR conditions, bound for cxy. (Capitol city airport, harrisburg, PA.) after takeoff from runway 30, I made a left turn eastbound, heading 090 degrees, and departed the area at 1000 ft MSL in order to remain well clear of overlying class B airspace. Once clear of class B, I climbed to 3500 ft and turned northeast to proceed on course. Remaining flight was uneventful. Upon arrival at cxy, I was given a phone numb by the ground controller for potomac approach, and was advised to call as soon as possible. After securing the aircraft, I called and was connected to an individual who idented himself as an ADIZ specialist. In the conversation that ensued, the gentleman informed me that by departing anp without a discrete transponder code, I was in violation of ADIZ airspace. I was advised that an investigation would take place and the matter would be referred to an FSDO for disposition. Cause of event: relative lack of recent operating experience in or near ADIZ airspace in VFR environment. In review, I determined that my error occurred when I assumed that by remaining clear of class B airspace I would also remain clear of the ADIZ. While I fly 15-16 days per month as a pilot in a part 121 operation, that is strictly an IFR environment, and did not prepare me for this airspace infraction while operating VFR during a pleasure flight. Remedy: refresher on airspace, controled and uncontrolled. Become familiar with ADIZ operations in VFR environment. I believe it would be helpful to depict ADIZ vertical limits, where it exists, in a manner similar to class B airspace, ie, FL180/surface.
Original NASA ASRS Text
Title: UNAUTH AND UNCOORD PENETRATION OF THE DC ADIZ AIRSPACE BY A NO FLT PLAN DEP C172 FROM ANP, MD.
Narrative: ON MAY/SAT/04, AT APPROX XA30L, I DEPARTED ANP, (LEE-ANNAPOLIS, MD) IN A C172, IN VFR CONDITIONS, BOUND FOR CXY. (CAPITOL CITY ARPT, HARRISBURG, PA.) AFTER TKOF FROM RWY 30, I MADE A L TURN EBOUND, HDG 090 DEGS, AND DEPARTED THE AREA AT 1000 FT MSL IN ORDER TO REMAIN WELL CLR OF OVERLYING CLASS B AIRSPACE. ONCE CLR OF CLASS B, I CLBED TO 3500 FT AND TURNED NE TO PROCEED ON COURSE. REMAINING FLT WAS UNEVENTFUL. UPON ARR AT CXY, I WAS GIVEN A PHONE NUMB BY THE GND CTLR FOR POTOMAC APCH, AND WAS ADVISED TO CALL ASAP. AFTER SECURING THE ACFT, I CALLED AND WAS CONNECTED TO AN INDIVIDUAL WHO IDENTED HIMSELF AS AN ADIZ SPECIALIST. IN THE CONVERSATION THAT ENSUED, THE GENTLEMAN INFORMED ME THAT BY DEPARTING ANP WITHOUT A DISCRETE XPONDER CODE, I WAS IN VIOLATION OF ADIZ AIRSPACE. I WAS ADVISED THAT AN INVESTIGATION WOULD TAKE PLACE AND THE MATTER WOULD BE REFERRED TO AN FSDO FOR DISPOSITION. CAUSE OF EVENT: RELATIVE LACK OF RECENT OPERATING EXPERIENCE IN OR NEAR ADIZ AIRSPACE IN VFR ENVIRONMENT. IN REVIEW, I DETERMINED THAT MY ERROR OCCURRED WHEN I ASSUMED THAT BY REMAINING CLR OF CLASS B AIRSPACE I WOULD ALSO REMAIN CLR OF THE ADIZ. WHILE I FLY 15-16 DAYS PER MONTH AS A PLT IN A PART 121 OP, THAT IS STRICTLY AN IFR ENVIRONMENT, AND DID NOT PREPARE ME FOR THIS AIRSPACE INFRACTION WHILE OPERATING VFR DURING A PLEASURE FLT. REMEDY: REFRESHER ON AIRSPACE, CTLED AND UNCTLED. BECOME FAMILIAR WITH ADIZ OPS IN VFR ENVIRONMENT. I BELIEVE IT WOULD BE HELPFUL TO DEPICT ADIZ VERT LIMITS, WHERE IT EXISTS, IN A MANNER SIMILAR TO CLASS B AIRSPACE, IE, FL180/SURFACE.
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.