A LR45 crew missed a OAK5 crossing restriction after departing runway 29 because a runway change req...

Attributes
ACN	863936
Time
Date	200912
Local Time Of Day	0601-1200
Place
Locale Reference	OAK.Airport
State Reference	CA
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Make Model Name	Learjet 45
Operating Under FAR Part	Part 91
Flight Phase	Initial Climb
Route In Use	SID OAK5
Flight Plan	IFR
Component
Aircraft Component	FMS/FMC
Person 1
Function	First Officer Pilot Not Flying
Qualification	Flight Crew Flight Instructor Flight Crew Instrument Flight Crew Multiengine Flight Crew Air Transport Pilot (ATP)
Experience	Flight Crew Last 90 Days 90 Flight Crew Total 11100 Flight Crew Type 900
Events
Anomaly	Deviation - Altitude Crossing Restriction Not Met Deviation - Procedural Published Material / Policy Deviation - Procedural Clearance

Narrative:

Flight was a reposition flight to a nearby airport. Total distance 20 NM. Captain on leg was inside aircraft doing interior preflight and getting the clearance. I was not flying the leg but did file the flight plan using my name as PIC. Outside I was de-icing; overseeing fueling and O2 replenishment. When all were accomplished we taxied out to the runway. When the checklist came to briefing the route the captain stated that we were given the oakland 5 departure and quote 'it's just a simple vector departure.' our charts are printed out but on efb's. I did not check this statement or pull up the SID. I was engrossed in our taxi route which was complex. This involved multiple hold shorts and 2 ground frequencies on the way to runway 29. I was following this closely on the efb. When we arrived at the departure end of the runway we were not ready for the departure; in hindsight. The cross 2000 ft from the oak VOR was not set. But our ultimate altitude of 5000 ft was in the altitude alerter. So as the captain climbed out; norcal told us to maintain 3000 ft which we did. Then informed us the oakland 5 had a crossing restriction 4 miles/2000 ft. Luckily no aircraft were on our TCAS and in short order were allowed to climb to 5000 ft.

Original NASA ASRS Text

Title: A LR45 crew missed a OAK5 crossing restriction after departing Runway 29 because a runway change required reprogramming the FMS and using an EFB airport chart for taxi guidance. The distractions caused the crew to miss the OAK5 crossing restriction.

Narrative: Flight was a reposition flight to a nearby airport. Total distance 20 NM. Captain on leg was inside aircraft doing interior preflight and getting the clearance. I was not flying the leg but did file the flight plan using my name as PIC. Outside I was de-icing; overseeing fueling and O2 replenishment. When all were accomplished we taxied out to the runway. When the checklist came to briefing the route the Captain stated that we were given the Oakland 5 Departure and Quote 'It's just a simple vector departure.' Our charts are printed out but on EFB's. I did not check this statement or pull up the SID. I was engrossed in our taxi route which was complex. This involved multiple hold shorts and 2 ground frequencies on the way to Runway 29. I was following this closely on the EFB. When we arrived at the departure end of the runway we were not ready for the departure; in hindsight. The cross 2000 FT from the OAK VOR was not set. But our ultimate altitude of 5000 FT was in the altitude alerter. So as the Captain climbed out; NORCAL told us to maintain 3000 FT which we did. Then informed us the Oakland 5 had a crossing restriction 4 miles/2000 FT. Luckily no aircraft were on our TCAS and in short order were allowed to climb to 5000 FT.

Data retrieved from NASA's ASRS site as of April 2012 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 LR45 crew missed a OAK5 crossing restriction after departing runway 29 because a runway change required reprogramming the FMS and using an efb airport chart for taxi guidance. The distractions caused the crew to miss the OAK5 crossing restriction.