2011-04 · NASA ASRS report 945941
A CE560 flight crew failed to comply with the initial altitude restrictions on the RUUDY RNAV SID from TEB when the Captain mistook the expected final altitude of FL400 as an initially cleared altitude of 4;000 FT.
When I picked up my clearance I was told there was a 50 minute delay and to call back in 45 minutes for engine start. While writing the clearance I was told this clearance: RUUDY 2; LANNA; expect FL400 in 10 minutes followed by a squawk and the departure frequency. I read back the clearance and after 45 minutes I contacted Gate Release for engine start. I was cleared to start and then told to contact Ground for taxi.After start the Co-Captain and I ran our checklist and briefed the departure. He questioned what I had in the altitude preselect. I looked at the clearance sheet and said I had received 4;000 FT and I had seen on the SID to maintain 1;500 FT to WENTZ and then 2;000 FT to TASCA or assigned by ATC. I had clearly misread the FL400 as 4;000 FT feet on initial climb out. I told the copilot to verify that with departure.When we checked in climbing through 2;100 FT we were told to maintain 2;000 FT. I immediately stopped my climb while in a turn to 260 degrees. Departure then told us to turn to 280 and maintain 2;000 FT; at which time he asked us what departure we were given. We initially said 4;000 FT; but were verifying that with Departure and he said; 'Who gave you 4;000 FT?' I had initially said Clearance; but it was clear after that I had read 4;000 FT instead of FL400.I have read that SID 100 times. It will not happen again. I phoned the Supervisor at NY TRACON and explained it to him and he was in agreement that I had misread my initial altitude.
Pilot Flying (PF) received clearance to from TEB clearance delivery as following:'Cleared via Ruddy2 departure; LANNA then as filed; expect flight level 400 ten minutes after departure. He was told to contact gate hold in 50 minutes before engine start. PF wrote clearance in shorthand as 'Ruddy2; LANNA AF; 40; squawk code; 126.7'.During taxi out; Pilot Not Flying (PNF) questioned initial altitude of 4000ft being different from what Ruddy2 departure instructed of 2000ft at TASCA. PF erroneously remembered and informed PNF that 4000ft was the initial assigned altitude. This was the result of the PF confusing '40' as meaning 4000ft initial altitude instead of the correct filed Flight Level 400 or FL400.Upon further review of the Ruddy2 departure by the PNF; and reading the instructions to 'cross TASCA at 2000 or as assigned by atc'; PNF was satisfied with the PF's confirmation of 4000ft being the initial altitude. During PNF's review of the Ruddy2 departure; PNF failed to point out to PF that the first instruction was to 'cross WENTZ at 1500ft'. This was partially due to PNF misunderstanding that this means to stop at 1500ft until WENTZ instead of his erroneous belief of cross WENTZ at or above 1500 ft.After departure from runway 24 and being handed off from TEB tower to New York departure; PNF checked in with NY departure stating '2000ft for 4000ft and heading 240. NY departure instructed us to immediately stop climb at 2000ft and then gave a heading of 260; which we complied with. This was just prior to intercepting the 260 degree course to WENTZ which requires a crossing at 1500ft. This was partially due to the crew's erroneous belief that 4000ft negated the altitudes assigned in the Ruddy2 departure.NY departure then questioned our clearance. PF then responded with 4000ft which was incorrectly believed to have been assigned by TEB clearance delivery. Before being handed off to New York Center; we were given the phone number to contact New York Tracon upon arrival.I believe these mistakes can be prevented by the crew members reviewing and briefing their clearance together prior to taxi. This will allow all crew members to give their undivided attention; which will facilitate a through and undistracted briefing; especially in a high workload environment such as TEB.
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.
Loading the flight search…
Pick an aircraft model — Boeing 737, Airbus A320, A380, Boeing 787 Dreamliner and more — enter your origin airport, and FlightFinder shows every route that plane flies from there with live fares.
We support Boeing 737/747/757/767/777/787, the full Airbus A220/A319/A320/A321/A330/A340/A350/A380 family, Embraer E170/E175/E190/E195, Bombardier CRJ and Dash 8, and the ATR 42/72 turboprops.
Search and schedules are free. Pro ($4.99/month, $39/year, or $99 one-time lifetime) unlocks the enriched flight card — on-time stats, CO₂ per passenger, amenities, live gate & weather — plus My Trips with push alerts.
Live schedules come from Amadeus, AeroDataBox and Travelpayouts. Observed routes (which aircraft actually flew a given city pair) are crowdsourced from adsb.lol ADS-B data under the Open Database License.