MU30 crew possible class D airspace violation.

Attributes
ACN	494110
Time
Date	200012
Day	Wed
Local Time Of Day	1201 To 1800
Place
Locale Reference	airport : aao.airport
State Reference	KS
Altitude	msl single value : 3000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tracon : ict.tracon
Operator	general aviation : corporate
Make Model Name	MU-300 Diamond 1/1A
Operating Under FAR Part	Part 91
Flight Phase	descent : intermediate altitude
Route In Use	approach : visual
Flight Plan	IFR
Aircraft 2
Controlling Facilities	tracon : ict.tracon
Make Model Name	Any Unknown or Unlisted Aircraft Manufacturer
Flight Phase	climbout : vacating altitude
Route In Use	departure : vfr
Person 1
Affiliation	company : corporate
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Experience	flight time last 90 days : 90 flight time total : 2200 flight time type : 200
ASRS Report	494110
Person 2
Affiliation	company : corporate
Function	flight crew : first officer
Qualification	pilot : instrument pilot : flight engineer pilot : atp pilot : multi engine pilot : commercial
Experience	flight time last 90 days : 120 flight time total : 4000 flight time type : 150
ASRS Report	494658
Events
Anomaly	airspace violation : entry non adherence : far
Independent Detector	other flight crewa
Resolutory Action	none taken : detected after the fact
Supplementary
Problem Areas	Chart Or Publication Flight Crew Human Performance ATC Human Performance
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

An IFR descent was initiated to land at aao from sgf. VFR conditions prevailed. The low chart for surrounding airspace was checked during descent. At 3000 ft MSL and 10 NM east of aao, ict approach reported 2 inbounds to aao with us being #1. The airport was in sight and IFR was canceled. Approach said to change to advisory frequency. During our descent to land on runway 36, we observed traffic on our skywatch which we first believed to be another inbound to zzo from the south. After visually acquiring the traffic, we determined the aircraft was departing bec airport. Visual contact was maintained and the traffic was not a conflict. We continued our position reports on aao CTAF and landed. After shutdown, we realized beech airport had a control tower on the field. No class D airspace on the commercial en route chart is depicted for beech airport. The very close proximity of the airports is a potential conflict for aircraft landing and departing both airports. Future incidents could be avoided if the close proximity were noted on the aao airport diagram.

Original NASA ASRS Text

Title: MU30 CREW POSSIBLE CLASS D AIRSPACE VIOLATION.

Narrative: AN IFR DSCNT WAS INITIATED TO LAND AT AAO FROM SGF. VFR CONDITIONS PREVAILED. THE LOW CHART FOR SURROUNDING AIRSPACE WAS CHKED DURING DSCNT. AT 3000 FT MSL AND 10 NM E OF AAO, ICT APCH RPTED 2 INBOUNDS TO AAO WITH US BEING #1. THE ARPT WAS IN SIGHT AND IFR WAS CANCELED. APCH SAID TO CHANGE TO ADVISORY FREQ. DURING OUR DSCNT TO LAND ON RWY 36, WE OBSERVED TFC ON OUR SKYWATCH WHICH WE FIRST BELIEVED TO BE ANOTHER INBOUND TO ZZO FROM THE S. AFTER VISUALLY ACQUIRING THE TFC, WE DETERMINED THE ACFT WAS DEPARTING BEC ARPT. VISUAL CONTACT WAS MAINTAINED AND THE TFC WAS NOT A CONFLICT. WE CONTINUED OUR POS RPTS ON AAO CTAF AND LANDED. AFTER SHUTDOWN, WE REALIZED BEECH ARPT HAD A CTL TWR ON THE FIELD. NO CLASS D AIRSPACE ON THE COMMERCIAL ENRTE CHART IS DEPICTED FOR BEECH ARPT. THE VERY CLOSE PROX OF THE ARPTS IS A POTENTIAL CONFLICT FOR ACFT LNDG AND DEPARTING BOTH ARPTS. FUTURE INCIDENTS COULD BE AVOIDED IF THE CLOSE PROX WERE NOTED ON THE AAO ARPT DIAGRAM.

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.