A320 was cleared to cross hayed intersection at FL190 but crossed at FL240 because FMC was updated incorrectly causing altitude constraints to be lost. Both rptrs cite aircraft equipment design as a contributing factor.

Home

Browse by month

Random

Latest

About

Contact

Attributes
ACN	369480
Time
Date	199705
Day	Sun
Local Time Of Day	1801 To 2400
Place
Locale Reference	atc facility : fqm
State Reference	PA
Altitude	msl bound lower : 19000 msl bound upper : 24000
Environment
Flight Conditions	Mixed
Light	Dusk
Aircraft 1
Controlling Facilities	artcc : zny
Operator	common carrier : air carrier
Make Model Name	A320
Operating Under FAR Part	Part 121
Navigation In Use	Other Other
Flight Phase	descent other
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Experience	flight time last 90 days : 200 flight time total : 10000 flight time type : 500
ASRS Report	369480
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : atp
Experience	flight time last 90 days : 90 flight time total : 7200 flight time type : 14
ASRS Report	369671
Events
Anomaly	altitude deviation : crossing restriction not met non adherence : clearance
Independent Detector	other controllera
Resolutory Action	none taken : detected after the fact
Consequence	Other
Supplementary
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

ATC cleared us to cross hayed at FL190, this was entered into the FMC. PF started the descent using VNAV. I proceeded to get ATIS, do a PA, and load the approach to ewr. When the approach is loaded into the FMC, all entered altitude constraints are lost. This was not noticed by PF or myself due to workload. ATC queried us 10 NM east of hayed if we received clearance to cross hayed at FL190, and if we were going to be able to make sweet intersection at 7000 ft. Replied 'yes' to both questions. High workload, compounded by significant software design failure that dumps entered data created this situation.

Original NASA ASRS Text

Title: A320 WAS CLRED TO CROSS HAYED INTXN AT FL190 BUT CROSSED AT FL240 BECAUSE FMC WAS UPDATED INCORRECTLY CAUSING ALT CONSTRAINTS TO BE LOST. BOTH RPTRS CITE ACFT EQUIP DESIGN AS A CONTRIBUTING FACTOR.

Narrative: ATC CLRED US TO CROSS HAYED AT FL190, THIS WAS ENTERED INTO THE FMC. PF STARTED THE DSCNT USING VNAV. I PROCEEDED TO GET ATIS, DO A PA, AND LOAD THE APCH TO EWR. WHEN THE APCH IS LOADED INTO THE FMC, ALL ENTERED ALT CONSTRAINTS ARE LOST. THIS WAS NOT NOTICED BY PF OR MYSELF DUE TO WORKLOAD. ATC QUERIED US 10 NM E OF HAYED IF WE RECEIVED CLRNC TO CROSS HAYED AT FL190, AND IF WE WERE GOING TO BE ABLE TO MAKE SWEET INTXN AT 7000 FT. REPLIED 'YES' TO BOTH QUESTIONS. HIGH WORKLOAD, COMPOUNDED BY SIGNIFICANT SOFTWARE DESIGN FAILURE THAT DUMPS ENTERED DATA CREATED THIS SIT.

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.