Date: 201310
Local time of day: 1801-2400
Location: CLT.Airport, NC
Flight conditions: VMC
Light: Night
Aircraft: B767-200
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Initial Approach
Airspace: Class B CLT
ATC / advisory: TRACON CLT
Reporter organization: Air Carrier
Reporter function: Pilot Not Flying; First Officer
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Workload; Situational Awareness
Anomaly: ATC Issue All Types; Deviation - Altitude Crossing Restriction Not Met; Deviation - Altitude Excursion From Assigned Altitude; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Automation Air Traffic Control; Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued Advisory / Alert; Flight Crew Became Reoriented; Flight Crew Returned To Clearance
Contributing factors: Procedure; Human Factors
Primary problem: Human Factors

Narrative: CLT ATIS states landing north; ILS 36R glideslope inoperative; VFR night conditions; light winds. IVANE 2 RNAV STAR was briefed and verified. ILS 36R was briefed with glideslope inoperative. VNAV procedures were briefed. We planned for a visual with VNAV back up for Runway 36R. Passing abeam CLT airport; CLT Approach descended us to 4;000 FT. We expected a short turn on to final. But; instead; they kept us down wind passed 20 miles. A right turn was issued; followed by another right turn; maintain 4;000 until passing HEKAM; cleared ILS approach 36R. The extended approach course was called for and drawn. But; it only extended to CIKDU; the FACF. Airplane is on autopilot and Captain pushed LOC to arm approach. HEKAM was not present on either FMS or HSI. I typed it into the FIX page to identify the fix to maintain 4;000; and told the Captain verbally. Airport was in sight; VASI was in sight. Airplane did not capture the LOC 36R. Captain clicked off autopilot to hand fly the approach; turning right to capture the LOC. We overshot the LOC and were correcting. We passed HEKAM at 4;000. 3;000 was set into the ALT window for CIKDU. We both became task saturated; because all fixes were not present; and Captain now hand flying. Captain started a descent passing HEKAM with airport in sight. CLT Approach called; maintain 3;500; and asked if we had traffic on left parallel runway. Captain called both traffic and airport in sight to ATC. It is not certain why the LOC did not capture by autopilot. The extended fixes did not load due to HEKAM transition not selected on FMS. Only the ILS 36R and STAR were loaded. Suddenly; our workload became high; trying to add missing fix and no autopilot. But Pilot Flying had airport and traffic in clear sight and continued. As Pilot Not Flying; my attention was divided; watching pilot hand flying; working the radio; and trying to find correct spelling of HEKAM and typing. A mistake was made by seeing 4;000 on the approach chart; not noticing that was LANSR; and then put the next altitude at 3;000 for CIKDU. We were misled by being at 4;000; 20 miles out. The proper altitude for HEKAM is 6;000; not 4;000 as assigned. Nor did ATC point out traffic on the parallel runway; when cleared for the approach on base; as 'heads up'. It was after the fact that ATC called out traffic. If ATC had said; maintain 4;000 to LANSR; for the attitude we were at; it would have helped in terms of situational awareness. ATC should use proper altitudes for fixes on extended approaches. Not a lower altitude. We were expecting a short approach based on an early descent to 4;000. It did not happen. Second; there should be some guidance about 'transitions' for airports that have them. We normally do not choose a transition and rarely use them; because they do not apply. Typically; it is obvious; but in this case; it is not. But with ever changing approaches and RNAV STARS or SIDS; what was meant to make our lives easier; is making it more complicated; because ATC always adds speed and altitude changes. Now the FMS can not predict what it needs to do. And; perhaps Special Notes should be added to the 'Airport pages'; where the use of 'transitions' is covered specifically with clear instructions to add it when loading the FMS; especially when we do not always frequent the airport on a regular basis. If not; then fixes will be missing. Lastly; a FMS 'interactive aid' should be added to our distance learning resources; to practice making last minute FMS changes. Then we can see what the FMS will do or not do for various profiles and scenarios. It is not practical to use the airplane; while on actual trips; because setting up scenarios is not very forgiving or gives us time to study the options or results.




Synopsis: Air Carrier First Officer reports that all the fixes necessary to fly the ILS36R at CLT do not load unless the HEKAM transition is selected when loading the ILS. Crew crosses HEKAM at 4;000 FT per ATC and starts descent to 3;000 FT not realising that two more fixes need to be crossed at 4;000 FT before descent is commenced. Glideslope was out of service.