 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
A C152 pilot, on a sightseeing flight, did not turn on his transponder, causing a violation of the washington dc ADIZ.
| Attributes | |
| ACN | 616573 |
| Time | |
| Date | 200405 |
| Day | Wed |
| Local Time Of Day | 1801 To 2400 |
| Place | |
| Locale Reference | airport : mtn.airport |
| State Reference | MD |
| Altitude | msl single value : 800 |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Controlling Facilities | tracon : pct.tracon tower : mtn.tower |
| Operator | general aviation : personal |
| Make Model Name | Cessna 152 |
| Operating Under FAR Part | Part 91 |
| Flight Phase | climbout : initial climbout : intermediate altitude climbout : takeoff |
| Route In Use | departure : vfr |
| Flight Plan | DVR |
| Person 1 | |
| Affiliation | other |
| Function | flight crew : single pilot |
| Qualification | pilot : instrument pilot : commercial pilot : cfi |
| Experience | flight time last 90 days : 45 flight time total : 295 flight time type : 1 |
| ASRS Report | 616573 |
| Person 2 | |
| Affiliation | government : faa |
| Function | controller : approach |
| Events | |
| Anomaly | airspace violation : entry non adherence : clearance non adherence : far non adherence : published procedure |
| Independent Detector | other controllera |
| Resolutory Action | none taken : detected after the fact |
| Consequence | faa : reviewed incident with flight crew faa : investigated |
| Supplementary | |
| Problem Areas | Flight Crew Human Performance |
| Primary Problem | Flight Crew Human Performance |
| Air Traffic Incident | Pilot Deviation |
Narrative:
I took off on a sight-seeing/intro flight in the evening. Run-up and takeoff procedures were uneventful, and during the pre-takeoff phase, I made sure that the transponder was turned on. Having only flown for .5 of an hour in this particular type of an airplane on a pervious occasion, I accidentally set the transponder to 'on,' instead of 'altitude'. Climbing through 800 ft MSL, I realized that the transponder should be set to 'altitude' (mode C) instead of 'on' and set it to 'altitude.' I believe my inexperience with a particular type of an airplane and the type of my mission (sight-seeing flight in congested airspace) may have led to me forgetting to place the transponder in the 'altitude' mode. I believe that closer inspection of the transponder before future flts will prevent a recurrence of this situation.
Original NASA ASRS Text
Title: A C152 PLT, ON A SIGHTSEEING FLT, DID NOT TURN ON HIS XPONDER, CAUSING A VIOLATION OF THE WASHINGTON DC ADIZ.
Narrative: I TOOK OFF ON A SIGHT-SEEING/INTRO FLT IN THE EVENING. RUN-UP AND TKOF PROCS WERE UNEVENTFUL, AND DURING THE PRE-TKOF PHASE, I MADE SURE THAT THE XPONDER WAS TURNED ON. HAVING ONLY FLOWN FOR .5 OF AN HR IN THIS PARTICULAR TYPE OF AN AIRPLANE ON A PERVIOUS OCCASION, I ACCIDENTALLY SET THE XPONDER TO 'ON,' INSTEAD OF 'ALT'. CLBING THROUGH 800 FT MSL, I REALIZED THAT THE XPONDER SHOULD BE SET TO 'ALT' (MODE C) INSTEAD OF 'ON' AND SET IT TO 'ALT.' I BELIEVE MY INEXPERIENCE WITH A PARTICULAR TYPE OF AN AIRPLANE AND THE TYPE OF MY MISSION (SIGHT-SEEING FLT IN CONGESTED AIRSPACE) MAY HAVE LED TO ME FORGETTING TO PLACE THE XPONDER IN THE 'ALT' MODE. I BELIEVE THAT CLOSER INSPECTION OF THE XPONDER BEFORE FUTURE FLTS WILL PREVENT A RECURRENCE OF THIS SIT.
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.