Small Aircraft; Low Wing; 1 Eng; Fixed Gear
Air Traffic Control Fully Certified
Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance; Ground Incursion Runway
Air Traffic Control Issued Advisory / Alert; Flight Crew Became Reoriented
Human Factors; Airport
I was the FLM for the shift; but was on break when Aircraft X was cleared for a visual approach to Runway 18 at LIT and was told to follow traffic.  The Aircraft X pilot had the traffic in sight and replied that he would follow the traffic.  He then descended and landed Runway 17 at ORK which is located 6 miles north of LIT and has a very similar runway configuration.  The CIC came and got me off of break and I entered the TRACON when the pilot cancelled IFR with LIT Tower and then departed ORK; VFR and landed LIT without incident.  I advised the Local Controller to have him call the Tower after he landed; but told the Local Controller that he did not need to give him the Brasher warning.  When the Aircraft X pilot called the TRACON I spoke with him and asked him what happened.  He advised that when he turned behind the traffic to follow he was lined up perfectly for Runway 17 at ORK and got focused on the runway and just landed there.  I told him that I was glad that he was safe and got his name and phone number and made a MOR entry on the log.
I was on an easterly heading northwest of Adams Field [LIT] at 3;000 FT MSL. I was cleared for the visual to 18 at Adams field and told to follow a King Air. When I turned to the south I misidentified Runway 17 at North Little Rock (ORK) as 18 at Adams. The runway lights were illuminated on Runway 17. At that point I lost visual contact with the King Air. I proceeded to land on 17 at ORK. This mistake could have been avoided by flying the approach to 18 at Adams using the navigational equipment available in the airplane.
A pilot and the LIT Tower Manager involved describe a landing at ORK Runway 17 while attempting to land at LIT on Runway 18.