A319 crew fails to meet crossing restr at druzz intersection.

Attributes
ACN	460393
Time
Date	200001
Day	Tue
Local Time Of Day	1201 To 1800
Place
Locale Reference	intersection : druzz
State Reference	VA
Altitude	msl bound lower : 15000 msl bound upper : 17300
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	artcc : zdc.artcc
Operator	common carrier : air carrier
Make Model Name	A319
Operating Under FAR Part	Part 121
Navigation In Use	other
Flight Phase	descent : intermediate altitude
Route In Use	arrival star : bucko 5
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : cfi pilot : commercial pilot : instrument pilot : multi engine pilot : atp
Experience	flight time last 90 days : 150 flight time total : 6100 flight time type : 340
ASRS Report	460393
Person 2
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : flight engineer pilot : atp
Experience	flight time last 90 days : 240 flight time total : 12800 flight time type : 750
ASRS Report	459973
Events
Anomaly	altitude deviation : undershoot altitude deviation : crossing restriction not met non adherence : clearance non adherence : published procedure other anomaly other
Independent Detector	other controllera
Resolutory Action	controller : issued new clearance flight crew : became reoriented
Supplementary
Problem Areas	Flight Crew Human Performance
Primary Problem	Flight Crew Human Performance

Narrative:

On descent into dca on bucko 5 (STAR), I (PNF) was off radio #1 to record ATIS and coordinate company gate assignment. While off, the captain (PF) received a descent clearance to cross druzz at 15000 ft. Captain programmed restr into FMGC. After receiving ATIS, captain inquired as to active runway. Runway switched from flight planned runway 19 to runway 1. While I was still on #2 radio with company, captain reprogrammed FMGC with runway 1. This re-strings arrival and has the effect of deleting programmed restrs. Aircraft defaults to vertical speed mode (ie, 1000 FPM). After speaking with company operations, I returned to #1 radio just in time to hear ATC ask if we would be able to meet restr at druzz. I replied negative, as I was unaware of the restr. ZDC reissued a clearance to 15000 ft (sans druzz) and we then expedited to 15000 ft crossing druzz at 17300 ft. Major causal factors included the captain. Operating single pilot and FMGC's tendency to delete arrival restrs with a runway change. Supplemental information from acn 459973: lessons learned: 1) must be much more alert when other pilot is out of the loop. 2) must be much more alert when descending in an excessive tailwind situation. 3) must be much more alert when having to reconfigure the mcdu/FMS during a managed descent after being assigned a crossing restr.

Original NASA ASRS Text

Title: A319 CREW FAILS TO MEET XING RESTR AT DRUZZ INTXN.

Narrative: ON DSCNT INTO DCA ON BUCKO 5 (STAR), I (PNF) WAS OFF RADIO #1 TO RECORD ATIS AND COORDINATE COMPANY GATE ASSIGNMENT. WHILE OFF, THE CAPT (PF) RECEIVED A DSCNT CLRNC TO CROSS DRUZZ AT 15000 FT. CAPT PROGRAMMED RESTR INTO FMGC. AFTER RECEIVING ATIS, CAPT INQUIRED AS TO ACTIVE RWY. RWY SWITCHED FROM FLT PLANNED RWY 19 TO RWY 1. WHILE I WAS STILL ON #2 RADIO WITH COMPANY, CAPT REPROGRAMMED FMGC WITH RWY 1. THIS RE-STRINGS ARR AND HAS THE EFFECT OF DELETING PROGRAMMED RESTRS. ACFT DEFAULTS TO VERT SPD MODE (IE, 1000 FPM). AFTER SPEAKING WITH COMPANY OPS, I RETURNED TO #1 RADIO JUST IN TIME TO HEAR ATC ASK IF WE WOULD BE ABLE TO MEET RESTR AT DRUZZ. I REPLIED NEGATIVE, AS I WAS UNAWARE OF THE RESTR. ZDC REISSUED A CLRNC TO 15000 FT (SANS DRUZZ) AND WE THEN EXPEDITED TO 15000 FT XING DRUZZ AT 17300 FT. MAJOR CAUSAL FACTORS INCLUDED THE CAPT. OPERATING SINGLE PLT AND FMGC'S TENDENCY TO DELETE ARR RESTRS WITH A RWY CHANGE. SUPPLEMENTAL INFO FROM ACN 459973: LESSONS LEARNED: 1) MUST BE MUCH MORE ALERT WHEN OTHER PLT IS OUT OF THE LOOP. 2) MUST BE MUCH MORE ALERT WHEN DSNDING IN AN EXCESSIVE TAILWIND SIT. 3) MUST BE MUCH MORE ALERT WHEN HAVING TO RECONFIGURE THE MCDU/FMS DURING A MANAGED DSCNT AFTER BEING ASSIGNED A XING RESTR.

Data retrieved from NASA's ASRS site as of July 2007 and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.