A falcon 2000 flight crew inbound to bfi got a late runway change and failed to properly reprogram t...

Attributes
ACN	743365
Time
Date	200706
Local Time Of Day	1201 To 1800
Place
Locale Reference	navaid : olm.vortac
State Reference	WA
Altitude	msl single value : 12000
Environment
Flight Conditions	Mixed
Light	Daylight
Aircraft 1
Controlling Facilities	tracon : s46.tracon
Operator	general aviation : corporate
Make Model Name	Falcon 2000
Operating Under FAR Part	Part 91
Navigation In Use	other other vortac
Flight Phase	descent : intermediate altitude
Route In Use	arrival star : olm
Flight Plan	IFR
Person 1
Affiliation	company : corporate
Function	flight crew : first officer
Qualification	pilot : atp
Experience	flight time last 90 days : 140 flight time total : 8000 flight time type : 375
ASRS Report	743365
Person 2
Affiliation	government : faa
Function	controller : approach
Events
Anomaly	altitude deviation : crossing restriction not met non adherence : clearance non adherence : published procedure
Independent Detector	other controllera
Resolutory Action	none taken : detected after the fact
Supplementary
Problem Areas	Flight Crew Human Performance
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

In flight we were given a clearance to 'descend via the OLM5 STAR.' they were landing south; but we had in runway 31L. The changes were made to the arrival; approach; and the runway. These were done individually. The falcon 2000 easy has a 'clear all' button to do the same thing all at once. The crossing at olm is 12000 ft 250 knots landing north; and 17000 ft 280 landing south. We crossed olm at 12000 ft when we should have been at 17000 ft. Upon review I have identified numerous errors. When changing runways; the use of the 'clear all' key is imperative. Changing each portion individually may not make all the adjustments to speed and altitude on an arrival. We noticed that the speed changed from 250 KTS to 280 KTS. I questioned the difference; and was side tracked by the heavy workload to not notice that the 12000 ft had not changed to 17000 ft. In my mind I had 12000 ft as the crossing altitude from our previous briefing; and the difference did not stand out until we were informed by the controller of our mistake. In the future; the 'clear all' key will be the only way to make changes to the arrival; approach; and landing runway. Also; upon receipt of any change; an entire new briefing will commence before addressing individual discrepancies. That should answer any questions; and bring to our attention all the changes.

Original NASA ASRS Text

Title: A FALCON 2000 FLT CREW INBOUND TO BFI GOT A LATE RWY CHANGE AND FAILED TO PROPERLY REPROGRAM THE FMS; RESULTING IN CROSSING OLM AT 12000 INSTEAD OF 17000 AS CHARTED.

Narrative: IN FLIGHT WE WERE GIVEN A CLEARANCE TO 'DESCEND VIA THE OLM5 STAR.' THEY WERE LANDING SOUTH; BUT WE HAD IN RWY 31L. THE CHANGES WERE MADE TO THE ARRIVAL; APPROACH; AND THE RWY. THESE WERE DONE INDIVIDUALLY. THE FALCON 2000 EASY HAS A 'CLEAR ALL' BUTTON TO DO THE SAME THING ALL AT ONCE. THE CROSSING AT OLM IS 12000 FT 250 KNOTS LANDING NORTH; AND 17000 FT 280 LANDING SOUTH. WE CROSSED OLM AT 12000 FT WHEN WE SHOULD HAVE BEEN AT 17000 FT. UPON REVIEW I HAVE IDENTIFIED NUMEROUS ERRORS. WHEN CHANGING RUNWAYS; THE USE OF THE 'CLEAR ALL' KEY IS IMPERATIVE. CHANGING EACH PORTION INDIVIDUALLY MAY NOT MAKE ALL THE ADJUSTMENTS TO SPEED AND ALTITUDE ON AN ARRIVAL. WE NOTICED THAT THE SPEED CHANGED FROM 250 KTS TO 280 KTS. I QUESTIONED THE DIFFERENCE; AND WAS SIDE TRACKED BY THE HEAVY WORKLOAD TO NOT NOTICE THAT THE 12000 FT HAD NOT CHANGED TO 17000 FT. IN MY MIND I HAD 12000 FT AS THE CROSSING ALTITUDE FROM OUR PREVIOUS BRIEFING; AND THE DIFFERENCE DID NOT STAND OUT UNTIL WE WERE INFORMED BY THE CONTROLLER OF OUR MISTAKE. IN THE FUTURE; THE 'CLEAR ALL' KEY WILL BE THE ONLY WAY TO MAKE CHANGES TO THE ARRIVAL; APPROACH; AND LANDING RUNWAY. ALSO; UPON RECEIPT OF ANY CHANGE; AN ENTIRE NEW BRIEFING WILL COMMENCE BEFORE ADDRESSING INDIVIDUAL DISCREPANCIES. THAT SHOULD ANSWER ANY QUESTIONS; AND BRING TO OUR ATTENTION ALL THE CHANGES.

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 falcon 2000 flight crew inbound to bfi got a late runway change and failed to properly reprogram the FMS; resulting in crossing olm at 12000 instead of 17000 as charted.