Corp small transport landing at wrong airport.

Attributes
ACN	100278
Time
Date	198812
Day	Tue
Local Time Of Day	0601 To 1200
Place
Locale Reference	airport : fyv airport : dak
State Reference	AR
Altitude	agl bound lower : 0 agl bound upper : 0
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tower : fyv
Operator	general aviation : corporate
Make Model Name	Small Transport, Low Wing, 2 Turboprop Eng
Flight Phase	landing other
Flight Plan	VFR
Person 1
Affiliation	Other
Function	flight crew : single pilot
Qualification	pilot : atp
Experience	flight time last 90 days : 110 flight time total : 9600
ASRS Report	100278
Events
Anomaly	non adherence : far other anomaly other other anomaly other
Independent Detector	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:

After being handed off from ZME VFR flight following approximately 10 mi out, I contacted springdale tower to get sequencing for landing. The local FBO replied on tower frequency that operations start at xb am, runway 18 in use. At about 5+ mi out (based upon RNAV readout date) I sighted what I thought was ags runway 18. I entered and announced a high and extended downwind for 18 ags, keeping in mind I was a transit and extra caution is needed in an unfamiliar environment. Turning base to final I heard an aircraft announce departure and then sighted a takeoff operation. Spacing was good and I announced final with the FBO acknowledging my transmission. I made final cockpit check of gear and flaps; checked airspeed and picture; T/D, rollout and turnoff into the terminal area which said 'fayetteville'--what? Fayetteville! Im' supposed to be in springdale! What the ? I quickly turned off taxiway, stopped and pulled the fayetteville plate and contacted ground control for a very embarrassing discussion. The location error was caused by improper validation of RNAV data input. I failed to double check input prior to final (input was 14 DME instead of 4 DME which is exactly the same distance difference between airports). The final check should also have included runway numbers to match approach plate landing data and less preoccupation on making a perfect landing.

Original NASA ASRS Text

Title: CORP SMT LNDG AT WRONG ARPT.

Narrative: AFTER BEING HANDED OFF FROM ZME VFR FLT FOLLOWING APPROX 10 MI OUT, I CONTACTED SPRINGDALE TWR TO GET SEQUENCING FOR LNDG. THE LCL FBO REPLIED ON TWR FREQ THAT OPS START AT XB AM, RWY 18 IN USE. AT ABOUT 5+ MI OUT (BASED UPON RNAV READOUT DATE) I SIGHTED WHAT I THOUGHT WAS AGS RWY 18. I ENTERED AND ANNOUNCED A HIGH AND EXTENDED DOWNWIND FOR 18 AGS, KEEPING IN MIND I WAS A TRANSIT AND EXTRA CAUTION IS NEEDED IN AN UNFAMILIAR ENVIRONMENT. TURNING BASE TO FINAL I HEARD AN ACFT ANNOUNCE DEP AND THEN SIGHTED A TKOF OPERATION. SPACING WAS GOOD AND I ANNOUNCED FINAL WITH THE FBO ACKNOWLEDGING MY XMISSION. I MADE FINAL COCKPIT CHK OF GEAR AND FLAPS; CHKED AIRSPD AND PICTURE; T/D, ROLLOUT AND TURNOFF INTO THE TERMINAL AREA WHICH SAID 'FAYETTEVILLE'--WHAT? FAYETTEVILLE! IM' SUPPOSED TO BE IN SPRINGDALE! WHAT THE ? I QUICKLY TURNED OFF TXWY, STOPPED AND PULLED THE FAYETTEVILLE PLATE AND CONTACTED GND CTL FOR A VERY EMBARRASSING DISCUSSION. THE LOCATION ERROR WAS CAUSED BY IMPROPER VALIDATION OF RNAV DATA INPUT. I FAILED TO DOUBLE CHK INPUT PRIOR TO FINAL (INPUT WAS 14 DME INSTEAD OF 4 DME WHICH IS EXACTLY THE SAME DISTANCE DIFFERENCE BTWN ARPTS). THE FINAL CHK SHOULD ALSO HAVE INCLUDED RWY NUMBERS TO MATCH APCH PLATE LNDG DATA AND LESS PREOCCUPATION ON MAKING A PERFECT LNDG.

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.