Charter aircraft using moving map for navigation enters class D airspace without contact.

Attributes
ACN	326362
Time
Date	199512
Day	Mon
Local Time Of Day	1201 To 1800
Place
Locale Reference	atc facility : fri
State Reference	KS
Altitude	msl bound lower : 2000 msl bound upper : 2000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Operator	common carrier : air taxi
Make Model Name	Small Aircraft
Navigation In Use	Other
Flight Phase	cruise other
Flight Plan	None
Person 1
Affiliation	Other
Function	flight crew : single pilot
Qualification	pilot : commercial pilot : instrument
Experience	flight time last 90 days : 50 flight time total : 7100
ASRS Report	326362
Events
Anomaly	non adherence : far other anomaly other
Independent Detector	other flight crewa
Resolutory Action	none taken : detected after the fact
Consequence	Other
Miss Distance	horizontal : 18000
Supplementary
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

While en route, utilizing argus 7000 EFIS moving map as primary navigation, coupled to garmin avd 100 GPS. I was negotiating the restr areas of ft riley. Navigating around their southern border was out of that airspace, but the ft riley army airfield was not depicted in the argus database. I blew through the traffic area at about 1000 ft AGL. No conflicts although there was a uh-1 about 2 mi at 11 O'clock to me. Now I had current charts on board which I referenced to for backup navigation, which I have always done. But after 1 yr of using the argus to get around various airspace beautifully, I was dismayed at this omission in their database. Databases are fallible. This is new technology that needs debugging. This was a real wake up call for me. The garmin did have it in their database. This was a good VFR day and I should have caught this on the chart, not relied on the electronic moving map.

Original NASA ASRS Text

Title: CHARTER ACFT USING MOVING MAP FOR NAV ENTERS CLASS D AIRSPACE WITHOUT CONTACT.

Narrative: WHILE ENRTE, UTILIZING ARGUS 7000 EFIS MOVING MAP AS PRIMARY NAV, COUPLED TO GARMIN AVD 100 GPS. I WAS NEGOTIATING THE RESTR AREAS OF FT RILEY. NAVING AROUND THEIR SOUTHERN BORDER WAS OUT OF THAT AIRSPACE, BUT THE FT RILEY ARMY AIRFIELD WAS NOT DEPICTED IN THE ARGUS DATABASE. I BLEW THROUGH THE TFC AREA AT ABOUT 1000 FT AGL. NO CONFLICTS ALTHOUGH THERE WAS A UH-1 ABOUT 2 MI AT 11 O'CLOCK TO ME. NOW I HAD CURRENT CHARTS ON BOARD WHICH I REFED TO FOR BACKUP NAV, WHICH I HAVE ALWAYS DONE. BUT AFTER 1 YR OF USING THE ARGUS TO GET AROUND VARIOUS AIRSPACE BEAUTIFULLY, I WAS DISMAYED AT THIS OMISSION IN THEIR DATABASE. DATABASES ARE FALLIBLE. THIS IS NEW TECHNOLOGY THAT NEEDS DEBUGGING. THIS WAS A REAL WAKE UP CALL FOR ME. THE GARMIN DID HAVE IT IN THEIR DATABASE. THIS WAS A GOOD VFR DAY AND I SHOULD HAVE CAUGHT THIS ON THE CHART, NOT RELIED ON THE ELECTRONIC MOVING MAP.

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.