Pilot of small aircraft VFR penetrated arsa.

Attributes
ACN	109025
Time
Date	198903
Day	Fri
Local Time Of Day	1201 To 1800
Place
Locale Reference	atc facility : fmy
State Reference	FL
Altitude	msl bound lower : 3500 msl bound upper : 3500
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tracon : rsw
Operator	general aviation : personal
Make Model Name	Small Aircraft, High Wing, 1 Eng, Fixed Gear
Flight Phase	cruise other
Flight Plan	None
Person 1
Affiliation	Other
Function	flight crew : single pilot
Qualification	pilot : private
Experience	flight time last 90 days : 50 flight time total : 2600 flight time type : 1400
ASRS Report	109025
Person 2
Affiliation	government : faa
Function	controller : approach
Qualification	controller : radar
Events
Anomaly	non adherence : far other anomaly other
Independent Detector	other controllera
Resolutory Action	none taken : detected after the fact
Consequence	faa : reviewed incident with flight crew
Supplementary
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

Inadvertent flight through arsa. I only knew I had flown through arsa after landing at naples, fl, and responding to request to phone ft myers approach. My flight began in taos, NM, with refueling stops in shreveport, la, and st petersburg, fl. Destination was naples. WX in fl was 4000' scattered clouds. Excellent VFR. Departed the arsa from st pete and attempted to contact ZMA for flight following. I had been with flight following ever since NM. ZMA did not respond on the published frequency. I then attempted to contact ft myers approach using the frequency published on the naples instrument approach plate, 119.00. No response. I was later told by ft myers the right frequency is 119.75. My first contact with naples was about 20 mi north of naples when I contacted the naples tower. The whole problem arose because the NOAA charts do not show arsa's--they show MOA's, restr areas, prohibited areas, warning areas, etc, special use airspace and TCA's, but not arsa's. There is no way to determine an arsa exists except on sectionals. This, and the frequency error, should be corrected on en route charts.

Original NASA ASRS Text

Title: PLT OF SMA VFR PENETRATED ARSA.

Narrative: INADVERTENT FLT THROUGH ARSA. I ONLY KNEW I HAD FLOWN THROUGH ARSA AFTER LNDG AT NAPLES, FL, AND RESPONDING TO REQUEST TO PHONE FT MYERS APCH. MY FLT BEGAN IN TAOS, NM, WITH REFUELING STOPS IN SHREVEPORT, LA, AND ST PETERSBURG, FL. DEST WAS NAPLES. WX IN FL WAS 4000' SCATTERED CLOUDS. EXCELLENT VFR. DEPARTED THE ARSA FROM ST PETE AND ATTEMPTED TO CONTACT ZMA FOR FLT FOLLOWING. I HAD BEEN WITH FLT FOLLOWING EVER SINCE NM. ZMA DID NOT RESPOND ON THE PUBLISHED FREQ. I THEN ATTEMPTED TO CONTACT FT MYERS APCH USING THE FREQ PUBLISHED ON THE NAPLES INSTRUMENT APCH PLATE, 119.00. NO RESPONSE. I WAS LATER TOLD BY FT MYERS THE RIGHT FREQ IS 119.75. MY FIRST CONTACT WITH NAPLES WAS ABOUT 20 MI N OF NAPLES WHEN I CONTACTED THE NAPLES TWR. THE WHOLE PROB AROSE BECAUSE THE NOAA CHARTS DO NOT SHOW ARSA'S--THEY SHOW MOA'S, RESTR AREAS, PROHIBITED AREAS, WARNING AREAS, ETC, SPECIAL USE AIRSPACE AND TCA'S, BUT NOT ARSA'S. THERE IS NO WAY TO DETERMINE AN ARSA EXISTS EXCEPT ON SECTIONALS. THIS, AND THE FREQ ERROR, SHOULD BE CORRECTED ON ENRTE CHARTS.

Data retrieved from NASA's ASRS site as of August 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.