A bronc intersection altitude constraint on the bos gardner SID was missed because the fix dropped o...

Attributes
ACN	763511
Time
Date	200711
Local Time Of Day	0601 To 1200
Place
Locale Reference	airport : bos.airport
State Reference	MA
Altitude	msl single value : 11000
Environment
Flight Conditions	VMC
Light	Dawn
Aircraft 1
Controlling Facilities	artcc : zbw.artcc
Operator	common carrier : air carrier
Make Model Name	A319
Operating Under FAR Part	Part 121
Navigation In Use	other
Flight Phase	descent : approach
Route In Use	arrival star : gdm
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : first officer
ASRS Report	763511
Person 2
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
ASRS Report	763757
Events
Anomaly	altitude deviation : crossing restriction not met non adherence : clearance non adherence : far non adherence : published procedure
Independent Detector	other flight crewa
Resolutory Action	none taken : anomaly accepted
Supplementary
Problem Areas	Aircraft Company Flight Crew Human Performance
Primary Problem	Flight Crew Human Performance

Narrative:

We were descending to bos on the gardner arrival; with a restr to cross bronc intersection at 11000 ft. This was placed in the FMC as a constraint. Later in the descent we became aware of a runway change. When that was programmed; the constraint at bronc was deleted. We became aware of this as we approached bronc with no time left to correct the difference. We crossed bronc higher than the restr. There was no communication with ATC regarding this. The flight continued with no further incident. With the different type of mcdu's we have; combined with the hour of the day and the high workload approaching the terminal area. It was easier than it should be to have missed this. Aside from the fact that we are ultimately responsible for where the aircraft should have ended up at bronc; to me; the concept of the automation is to help in reducing our workload. The fact that once we placed the constraint in the FMC and then had to remember to do it again after the runway change mitigates that purpose.

Original NASA ASRS Text

Title: A BRONC INTXN ALT CONSTRAINT ON THE BOS GARDNER SID WAS MISSED BECAUSE THE FIX DROPPED OUT FOLLOWING A RWY CHANGE AND AN MCDU REPROGRAM TO THE NEW RWY.

Narrative: WE WERE DSNDING TO BOS ON THE GARDNER ARR; WITH A RESTR TO CROSS BRONC INTXN AT 11000 FT. THIS WAS PLACED IN THE FMC AS A CONSTRAINT. LATER IN THE DSCNT WE BECAME AWARE OF A RWY CHANGE. WHEN THAT WAS PROGRAMMED; THE CONSTRAINT AT BRONC WAS DELETED. WE BECAME AWARE OF THIS AS WE APCHED BRONC WITH NO TIME LEFT TO CORRECT THE DIFFERENCE. WE CROSSED BRONC HIGHER THAN THE RESTR. THERE WAS NO COM WITH ATC REGARDING THIS. THE FLT CONTINUED WITH NO FURTHER INCIDENT. WITH THE DIFFERENT TYPE OF MCDU'S WE HAVE; COMBINED WITH THE HOUR OF THE DAY AND THE HIGH WORKLOAD APCHING THE TERMINAL AREA. IT WAS EASIER THAN IT SHOULD BE TO HAVE MISSED THIS. ASIDE FROM THE FACT THAT WE ARE ULTIMATELY RESPONSIBLE FOR WHERE THE ACFT SHOULD HAVE ENDED UP AT BRONC; TO ME; THE CONCEPT OF THE AUTOMATION IS TO HELP IN REDUCING OUR WORKLOAD. THE FACT THAT ONCE WE PLACED THE CONSTRAINT IN THE FMC AND THEN HAD TO REMEMBER TO DO IT AGAIN AFTER THE RWY CHANGE MITIGATES THAT PURPOSE.

Data retrieved from NASA's ASRS site as of January 2009 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.

A bronc intersection altitude constraint on the bos gardner SID was missed because the fix dropped out following a runway change and an mcdu reprogram to the new runway.