Given a speed restr in their original clearance, but having no way to set a reminder, it is overlook...

Attributes
ACN	526680
Time
Date	200110
Day	Fri
Local Time Of Day	1201 To 1800
Place
Locale Reference	atc facility : sct.tracon
State Reference	CA
Altitude	msl bound lower : 10000 msl bound upper : 23000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	artcc : zla.artcc
Operator	general aviation : corporate
Make Model Name	Falcon 50
Flight Phase	climbout : vacating altitude climbout : intermediate altitude
Route In Use	departure sid : van nuys
Flight Plan	IFR
Person 1
Affiliation	company : corporate
Function	flight crew : first officer
Qualification	pilot : atp
Experience	flight time last 90 days : 100 flight time total : 3300 flight time type : 400
ASRS Report	526680
Events
Anomaly	non adherence : clearance other anomaly
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:

Received ATC clearance through pre departure clearance. The clearance included 'maintain 250 KTS until advised.' with the company policy of airspeed bug settings there was not a way to set a bug to remind us of this speed. When we, as a crew, reviewed the clearance, we looked only at the first page displayed on the FMS. There was nothing on the departure procedure about maintaining 250 KTS. The first couple of departure controllers said nothing to us about a speed to maintain. When we were talking to the third controller after departure, he asked about our speed which was much faster than 250 KTS. It was clearly our fault for not complying with the speed on departure. I read the clearance completely when I first got it, yet there was no way to set a speed for departure. Thinking back, I could have entered it in the FMS like we do regularly for arrs. As a crew, we should have reviewed the entire clearance not just the routing and altitude. On departure, the tower verified the heading we needed to turn to twice, which was printed on the departure chart. Yet, no mention of speed was made until passing FL230. It may be a good idea to put the 250 KT speed on the departure chart if it is SOP at burbank.

Original NASA ASRS Text

Title: GIVEN A SPD RESTR IN THEIR ORIGINAL CLRNC, BUT HAVING NO WAY TO SET A REMINDER, IT IS OVERLOOKED UNTIL THE THIRD CTLR HANDLING THE FLT REQUESTED SPD WHICH AT THE TIME WAS MUCH HIGHER THAN CLRED.

Narrative: RECEIVED ATC CLRNC THROUGH PDC. THE CLRNC INCLUDED 'MAINTAIN 250 KTS UNTIL ADVISED.' WITH THE COMPANY POLICY OF AIRSPD BUG SETTINGS THERE WAS NOT A WAY TO SET A BUG TO REMIND US OF THIS SPD. WHEN WE, AS A CREW, REVIEWED THE CLRNC, WE LOOKED ONLY AT THE FIRST PAGE DISPLAYED ON THE FMS. THERE WAS NOTHING ON THE DEP PROC ABOUT MAINTAINING 250 KTS. THE FIRST COUPLE OF DEP CTLRS SAID NOTHING TO US ABOUT A SPD TO MAINTAIN. WHEN WE WERE TALKING TO THE THIRD CTLR AFTER DEP, HE ASKED ABOUT OUR SPD WHICH WAS MUCH FASTER THAN 250 KTS. IT WAS CLRLY OUR FAULT FOR NOT COMPLYING WITH THE SPD ON DEP. I READ THE CLRNC COMPLETELY WHEN I FIRST GOT IT, YET THERE WAS NO WAY TO SET A SPD FOR DEP. THINKING BACK, I COULD HAVE ENTERED IT IN THE FMS LIKE WE DO REGULARLY FOR ARRS. AS A CREW, WE SHOULD HAVE REVIEWED THE ENTIRE CLRNC NOT JUST THE ROUTING AND ALT. ON DEP, THE TWR VERIFIED THE HEADING WE NEEDED TO TURN TO TWICE, WHICH WAS PRINTED ON THE DEP CHART. YET, NO MENTION OF SPD WAS MADE UNTIL PASSING FL230. IT MAY BE A GOOD IDEA TO PUT THE 250 KT SPD ON THE DEP CHART IF IT IS SOP AT BURBANK.

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.

Given a speed restr in their original clearance, but having no way to set a reminder, it is overlooked until the third controller handling the flight requested speed which at the time was much higher than cleared.