Narrative:

Ferry flight to hks. Clearance from meridian to destination due to military area. We had a clearance of 17;000 MSL over meridian to the airport; then subsequently cleared to 2;000 MSL. At approximately 10-12 SM east northeast the pilot monitoring said he had the airport in sight and ATC cleared us for the visual approach runway 16 into hks. With our approaching angle to the airport we were on a 240 degree heading visually; an 80 degree intercept angle to runway 16. We were configured for flaps 1 and gear down; making the left turn and selecting 'vectors to final' and selecting app mode. I noticed on the approach plate of my pfd and on the mfd map that the approach was not loading properly and confirming my 'track' for a 6 SM final. It did not confirm on the pfd and mfd screens respectively. As I stated to the pilot monitoring that the approach and profile did not correlate; ATC said; 'it looks like you are lining up for the wrong airport (jan).' we immediately acknowledged and accepted. We were approximately 1;600 MSL and 6 miles from the runway. ATC gave us a clearance to climb to 2;000 MSL and a heading of 270 degrees and stated hks (hawkins) airport is two o'clock and 7 miles. With the close proximity and same runway as hks; airport jan was easily mistaken. We maintained present airspeed and complied with the clearance. Once we visually identified and confirmed hks airport we were cleared for the visual runway 16 and we proceeded accordingly and landed.both pilots need to confirm the airport before reporting to ATC. Confirm the automation visually with all the parameters and resources available. Back up the automation to that which is visually seen. Effective communication and action.

Google
 

Original NASA ASRS Text

Title: Corporate Captain reported lining up for the wrong airport during a visual approach to HKS airport.

Narrative: Ferry flight to HKS. Clearance from Meridian to destination due to Military Area. We had a clearance of 17;000 MSL over Meridian to the airport; then subsequently cleared to 2;000 MSL. At approximately 10-12 SM east northeast the pilot monitoring said he had the airport in sight and ATC cleared us for the Visual Approach Runway 16 into HKS. With our approaching angle to the airport we were on a 240 degree heading visually; an 80 degree intercept angle to Runway 16. We were configured for flaps 1 and gear down; making the left turn and selecting 'Vectors to Final' and selecting APP Mode. I noticed on the approach plate of my PFD and on the MFD map that the approach was not loading properly and confirming my 'Track' for a 6 SM final. It did not confirm on the PFD and MFD screens respectively. As I stated to the pilot monitoring that the approach and profile did not correlate; ATC said; 'It looks like you are lining up for the wrong airport (JAN).' We immediately acknowledged and accepted. We were approximately 1;600 MSL and 6 miles from the runway. ATC gave us a clearance to climb to 2;000 MSL and a heading of 270 degrees and stated HKS (Hawkins) airport is two o'clock and 7 miles. With the close proximity and same runway as HKS; airport JAN was easily mistaken. We maintained present airspeed and complied with the clearance. Once we visually identified and confirmed HKS Airport we were cleared for the visual Runway 16 and we proceeded accordingly and landed.Both pilots need to confirm the airport before reporting to ATC. Confirm the automation visually with all the parameters and resources available. Back up the automation to that which is visually seen. Effective communication and action.

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