37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 590051 |
Time | |
Date | 200308 |
Day | Mon |
Local Time Of Day | 0601 To 1200 |
Place | |
Locale Reference | airport : ryn.airport |
State Reference | AZ |
Altitude | agl single value : 5500 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tracon : u90.tracon tower : ryn.tower |
Operator | general aviation : personal |
Make Model Name | Skyhawk 172/Cutlass 172 |
Operating Under FAR Part | Part 91 |
Flight Phase | cruise : level descent : approach landing : roll |
Flight Plan | None |
Person 1 | |
Affiliation | other |
Function | flight crew : single pilot |
Qualification | pilot : commercial pilot : instrument pilot : cfi |
Experience | flight time last 90 days : 25 flight time total : 360 flight time type : 60 |
ASRS Report | 590051 |
Person 2 | |
Affiliation | other |
Function | observation : observer |
Qualification | pilot : private pilot : instrument |
Experience | flight time last 90 days : 20 flight time total : 240 flight time type : 10 |
ASRS Report | 590052 |
Events | |
Anomaly | airspace violation : entry non adherence : far non adherence : published procedure |
Independent Detector | other controllera |
Resolutory Action | controller : issued new clearance |
Consequence | faa : reviewed incident with flight crew |
Supplementary | |
Problem Areas | Navigational Facility FAA Flight Crew Human Performance Airspace Structure |
Primary Problem | Ambiguous |
Air Traffic Incident | Pilot Deviation |
Narrative:
I was transporting a cessna 172SP, from our base in glendale, az, to our facility on ryan field near tucson, az. At my time of arrival, there was an active NOTAM, stating a transponder code and approach control radar vectors were required within 30 NM of the tus VOR. My route to ryn took me about 5 mi into the 30 NM veil of the tus VOR NOTAM. Prior to my flight, I checked the WX and flight information for both geu and ryn airports, I did not check information for tus. Neither the geu nor ryn NOTAMS stated anything about the tucson NOTAM which, in effect, closed the ryn airspace. Ryn is outside of the tucson airspace. When my flight was 12 NM northwest of ryn I contacted the ryn tower for landing information and clearance instructions. I was then instructed to contact tucson approach. I was then given a squawk code and vectors for landing at ryn. Upon landing I was instructed to notify tucson tower. I gave them my pilot number and contact information. I feel if a NOTAM or other regulation encompasses a number of airports, that NOTAM should be issued for each facility affected. Ryn NOTAMS dealt with the construction on the field at that time, not the fdc NOTAM issued at tucson which encompassed the ryan airport.
Original NASA ASRS Text
Title: A C172 PLT AND OBSERVER MANAGE TO PENETRATE A NOTAMED AREA AROUND TUS VOR WHEN ON A REPOSITIONING FLT TO RYN, AZ.
Narrative: I WAS TRANSPORTING A CESSNA 172SP, FROM OUR BASE IN GLENDALE, AZ, TO OUR FACILITY ON RYAN FIELD NEAR TUCSON, AZ. AT MY TIME OF ARR, THERE WAS AN ACTIVE NOTAM, STATING A XPONDER CODE AND APCH CTL RADAR VECTORS WERE REQUIRED WITHIN 30 NM OF THE TUS VOR. MY RTE TO RYN TOOK ME ABOUT 5 MI INTO THE 30 NM VEIL OF THE TUS VOR NOTAM. PRIOR TO MY FLT, I CHKED THE WX AND FLT INFO FOR BOTH GEU AND RYN ARPTS, I DID NOT CHK INFO FOR TUS. NEITHER THE GEU NOR RYN NOTAMS STATED ANYTHING ABOUT THE TUCSON NOTAM WHICH, IN EFFECT, CLOSED THE RYN AIRSPACE. RYN IS OUTSIDE OF THE TUCSON AIRSPACE. WHEN MY FLT WAS 12 NM NW OF RYN I CONTACTED THE RYN TWR FOR LNDG INFO AND CLRNC INSTRUCTIONS. I WAS THEN INSTRUCTED TO CONTACT TUCSON APCH. I WAS THEN GIVEN A SQUAWK CODE AND VECTORS FOR LNDG AT RYN. UPON LNDG I WAS INSTRUCTED TO NOTIFY TUCSON TWR. I GAVE THEM MY PLT NUMBER AND CONTACT INFO. I FEEL IF A NOTAM OR OTHER REG ENCOMPASSES A NUMBER OF ARPTS, THAT NOTAM SHOULD BE ISSUED FOR EACH FACILITY AFFECTED. RYN NOTAMS DEALT WITH THE CONSTRUCTION ON THE FIELD AT THAT TIME, NOT THE FDC NOTAM ISSUED AT TUCSON WHICH ENCOMPASSED THE RYAN ARPT.
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.