Date: 201205
Local time of day: 1801-2400
Location: ZLA.ARTCC, CA
Flight conditions: VMC
Light: Night
Aircraft: A320
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Descent
Airspace: Class A ZLA
ATC / advisory: Center ZLA
Aircraft component: Autopilot
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Communication Breakdown; Confusion; Situational Awareness; Human-Machine Interface
Anomaly: Aircraft Equipment Problem Less Severe; Deviation - Altitude Crossing Restriction Not Met; Deviation - Altitude Overshoot; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Became Reoriented; Flight Crew Overcame Equipment Problem; Flight Crew Returned To Clearance; General Maintenance Action
Contributing factors: Aircraft; Human Factors
Primary problem: Aircraft

Narrative: On descent into LAX out of FL300 on the SEAVU2 arrival the FMGC in our aircraft would not hold the programmed airspeed entered in the perf descent page (ATC assigned 300+ knots; then later assigned 280 KIAS). I tried several times to select managed speed and was forced by the aircraft (it was pitching up trying incorrectly to achieve 250 KIAS) to return to selected speed and after three attempts found myself almost 1;000 FT above path. (I wrote up the anomalies upon arrival in LAX).In order to make my restriction of 17;000 FT/280 KTS at KONZL; I selected full speed brakes and disconnected the autopilot (in order to get full spoiler deflection). We monitored our speed and vertical path and managed to meet the constraint airspeed and altitude at KONZL. As we approached ENGLI we noticed that we were starting to descend below the constraint altitude approximately two and a half miles prior to the fix. I pushed V/S to stop our descent and was surprised that we continued a gentle descent. At the same time we noticed that the NAV display was indicating that we were 0.3 miles right of course centerline. At this time the First Officer noticed that we were not following the Flight Director. I realized that after stowing the speed brake we had never reengaged the autopilot and the airplane had been tracking pitch and roll attitude in Control Wheel Steering since the speed brakes had been stowed.We crossed close abeam ENGLI at approximately 15;600 FT (almost 400 FT below constant altitude). A quick visual scan and scan of the TCAS indicated that we were not in danger of a midair collision. A gentle correction to our descent rate reestablished us on path and the autopilot was reengaged. We advised ATC that we were going to miss our altitude constraint at ENGLI. The rest of the approach was flown within parameters and without incident.The event was caused by our distraction with equipment malfunction and failure to remain aware of the autopilot disconnect. Because Control Wheel Steering is the automatic default in the A320 it can easily be mistaken for an autopilot engaged mode.We needed better delineation of pilot flying and pilot not flying duties. Only close attention to the path allowed us to catch it (the autopilot disconnect) as early as we did.




Synopsis: An A320 Captain discussed the effects of flight crew confusion and distraction associated with a malfunctioning vertical navigation programming on flight path control and situational awareness.