Date: 201303
Local time of day: 1201-1800
Location: BWI.Airport, MD
Flight conditions: VMC
Light: Daylight
Aircraft: A320
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Descent
Airspace: Class B BWI
ATC / advisory: TRACON PCT
Reporter organization: Air Carrier
Reporter function: Pilot Flying; Check Pilot; Captain
Human factors: Workload; Fatigue; Confusion
Anomaly: Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Became Reoriented
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: I was giving the first leg of Operating Experience (OE) to a new hire First Officer. This was the 6th straight day of work; which had included early morning wake-ups and the first two legs had been cancelled from our trip; however we had already checked in early because the First Officer was a new hire and needed an introductory briefing. Our aircraft had an MEL for an inoperative IDG; which required repetitive maintenance action. It was a short leg; so I flew so the new First Officer would have time to settle in. At first ATC check in; Approach cleared us to cross SABBI at 15;000 on the RAVNN 3 arrival. Shortly after crossing SABBI; we were given a 070 heading with descent to 8;000. After leaving the arrival for a period of time; we were given direct to RAVNN and cross RAVNN at 6;000. Because RAVNN was noted 'for Runway 33; expect radar vectors'; it was my assumption that we were simply going direct to a fix with a crossing restriction (all intervening fixes were deleted) and no longer on the STAR. The ATIS stated that Runway 33L visual approaches were in use; and I cleared the additional legs beyond that point from the FMS so it would be easier for the First Officer to clean up the FMS when we were on vectors. Approaching RAVNN; we were given a frequency change and the new Controller cleared us to 5;000. Remembering that Maintenance had not acted to comply with the MEL to check APU oil on each departure; I asked the First Officer to make sure that Operations had notified Contract Maintenance to accomplish the MEL follow-up action. Shortly after crossing RAVNN and now on a 050 heading; the Controller asked why we did not proceed to NAVEY (the fix beyond RAVNN's 'Runway 33 expect radar vectors' notation). I simply replied that we had been expecting radar vectors as noted. The Controller then cleared us direct to the FAF and subsequently for a visual approach.Although the assumption that we would be given radar vectors (as noted on the approach chart) was the primary cause; contributing was my personal fatigue at the end of a 6 day stretch of early mornings; as well as the task loading associated with OE for a highly inexperienced First Officer and the additional task-loading while making sure that our MEL follow-up action was going to be accomplished.




Synopsis: A320 Check Airman conducting IOE; neglected to proceed to the next approach fix on an arrival procedure.