Medium Transport; Low Wing; 2 Turbojet Eng
Confusion; Fatigue; Situational Awareness
Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter CFTT / CFIT
Flight Crew Became Reoriented; Flight Crew Executed Go Around / Missed Approach; Flight Crew FLC complied w / Automation / Advisory
Airport; Human Factors
We were cleared for visual approach and to land 10R LAN.  We intercepted LOC and GS did not look right.  It did not concur with PAPI.  We continued using PAPI info.  About 500 feet got obstacle pull up aural alert and initiated a missed approach.  Told ATC that we were going missed and he gave us heading and altitude and I told him that our intention was to land 28L now.  We completed flight without further incident. Got in late night before (midnight) and didn't get to sleep until about XA:00.  Woke up XF:30.  Late show next day and 3 plus hour leg.  Arrived there in time to get something to eat and attempt a short nap.  Short flight to LAN complicated by Weather.  Took 1 hour to deice and this made our arrival over 30 late.  Therefore we requested 10 though the ATIS called for 28.  Controller granted request and said he switched LOC for us. This was why I wasn't that concerned with PAPI and GS discrepancy.  I thought maybe it wasn't done right.  It was.  I had lost my situational awareness and hadn't backed up what was happening checking the FMS properly.   We were approaching 9 at 4D0 [Abrams Muni] which was collocated with FAF for 10R and I was looking at that waypoint as the field.  As we were climbing on the missed I saw on the FMS that 10R was still in front of us and then saw 10R.  Realizing we had approached the wrong runway.  Being extra vigilant knowing I was tired and we were beyond when I thought I would be done. I should have seen the discrepancy sooner- before we started descending.  The information was there I didn't see it.  A note on the -7 [Chart] might help as well.  That runway was lit up like a Christmas tree and is on the extended line of 10R.
Air Carrier Captain reports mistaking 4D0 for Runway 10R at LAN (6 NM west) until EGPWS alerts for an obstacle an a go-around is initiated.