Penetration of arsa not depicted on low altitude enroute chart.

Attributes
ACN	116100
Time
Date	198906
Day	Fri
Local Time Of Day	0601 To 1200
Place
Locale Reference	atc facility : evv
State Reference	IN
Altitude	msl bound lower : 3500 msl bound upper : 3500
Environment
Flight Conditions	VMC
Light	Dusk
Aircraft 1
Controlling Facilities	tracon : evv
Operator	general aviation : corporate
Make Model Name	Small Transport, Low Wing, 2 Recip Eng
Flight Phase	cruise other
Flight Plan	None
Person 1
Affiliation	Other
Function	flight crew : single pilot
Qualification	pilot : commercial pilot : atp
Experience	flight time last 90 days : 150 flight time total : 4400 flight time type : 35
ASRS Report	116100
Person 2
Affiliation	government : faa
Function	controller : handoff position
Qualification	controller : radar
Events
Anomaly	other anomaly other other anomaly other
Independent Detector	other controllera other flight crewa
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:

I was flying at a cruise altitude of 3500 asl in an small transport while penetration of the evansville, in arsa occurred. The WX was very hazy, there was 5 mi visibility, and the flight was conducted under VFR flight conditions. I was navigating from the pocket city VOR to the louisville VOR using a combined low en route chart and a 1:5000,000 VFR chart. While using the low en route chart through the evansville area, I did not detect any indication of an arsa. Prior to entering louisville arsa proper contact was used to call the controling facility. With a destination of lexington, ky, louisville approach control advised me to call lexington tower. At that point it was evident something was wrong. Referring to my VFR chart I saw I had passed through the evansville arsa by 1 mi. After landing at lexington I called the tower immediately to explain what had happened. I requested the phone # of the supervisor at evansville controling facility and called the supervisor to discuss the matter. I asked if he needed a written report, he said no and asked me for my name and phone #. He informed me to expect a phone call from the FAA GADO. I did my best to inform all controling facs about what had happened. Please note: low en route charts depict all TCA's, why not arsa's?

Original NASA ASRS Text

Title: PENETRATION OF ARSA NOT DEPICTED ON LOW ALT ENROUTE CHART.

Narrative: I WAS FLYING AT A CRUISE ALT OF 3500 ASL IN AN SMT WHILE PENETRATION OF THE EVANSVILLE, IN ARSA OCCURRED. THE WX WAS VERY HAZY, THERE WAS 5 MI VISIBILITY, AND THE FLT WAS CONDUCTED UNDER VFR FLT CONDITIONS. I WAS NAVIGATING FROM THE POCKET CITY VOR TO THE LOUISVILLE VOR USING A COMBINED LOW ENRTE CHART AND A 1:5000,000 VFR CHART. WHILE USING THE LOW ENRTE CHART THROUGH THE EVANSVILLE AREA, I DID NOT DETECT ANY INDICATION OF AN ARSA. PRIOR TO ENTERING LOUISVILLE ARSA PROPER CONTACT WAS USED TO CALL THE CTLING FAC. WITH A DEST OF LEXINGTON, KY, LOUISVILLE APCH CTL ADVISED ME TO CALL LEXINGTON TWR. AT THAT POINT IT WAS EVIDENT SOMETHING WAS WRONG. REFERRING TO MY VFR CHART I SAW I HAD PASSED THROUGH THE EVANSVILLE ARSA BY 1 MI. AFTER LNDG AT LEXINGTON I CALLED THE TWR IMMEDIATELY TO EXPLAIN WHAT HAD HAPPENED. I REQUESTED THE PHONE # OF THE SUPVR AT EVANSVILLE CTLING FAC AND CALLED THE SUPVR TO DISCUSS THE MATTER. I ASKED IF HE NEEDED A WRITTEN REPORT, HE SAID NO AND ASKED ME FOR MY NAME AND PHONE #. HE INFORMED ME TO EXPECT A PHONE CALL FROM THE FAA GADO. I DID MY BEST TO INFORM ALL CTLING FACS ABOUT WHAT HAD HAPPENED. PLEASE NOTE: LOW ENRTE CHARTS DEPICT ALL TCA'S, WHY NOT ARSA'S?

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.