37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1081204 |
Time | |
Date | 201304 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | TEB.Airport |
State Reference | NJ |
Environment | |
Flight Conditions | VMC |
Light | Dusk |
Aircraft 1 | |
Make Model Name | Gulfstream G200 (IAI 1126 Galaxy) |
Operating Under FAR Part | Part 91 |
Flight Phase | Initial Climb |
Route In Use | SID RUUDY 4 |
Flight Plan | IFR |
Component | |
Aircraft Component | Altitude Alert |
Person 1 | |
Function | First Officer Pilot Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) Flight Crew Flight Instructor Flight Crew Instrument Flight Crew Multiengine |
Experience | Flight Crew Last 90 Days 50 Flight Crew Total 10050 Flight Crew Type 2000 |
Events | |
Anomaly | Deviation - Altitude Crossing Restriction Not Met Deviation - Altitude Overshoot Deviation - Procedural Published Material / Policy |
Narrative:
Departing teb on the ruudy departure; the captain was the non flying pilot in the right seat and I was the sic/flying pilot; but sitting in the left seat. The captain deplaned the passengers; handled the luggage and paid the applicable fees then returned to the plane while I received the pre departure clearance and set up the FMS for departure. The ruudy SID has a final altitude of 2;000 (or as assigned) with an intermediate stop at 1;500 until crossing wentz. The captain set 2;000 in the altitude preselect which should have been 1;500. He then briefed the clearance. As the flying pilot I considered the noise abatement for the teterboro area and intended to climb as expeditiously as possible to the initial altitude. We discussed 1;500 at wentz then the climb to 2;000 over tasca however I didn't catch that the captain had set 2;000 in the altitude preselect. The chain of events was: 1. The incorrect setting of the altitude preselect; 2. Preoccupation with noise abatement; 3. I followed the flight director to the preselected altitude. I should have been able to break the error chain simply by noting the incorrect setting of the initial altitude rather than trusting what was set to be correct.
Original NASA ASRS Text
Title: A Gulfstream flight crew departing TEB on the RUUDY RNAV SID failed to cross WENTZ at 1;500 MSL as required. A contributing factor was setting the final SID altitude; 2;000 MSL; in the altitude alert window rather than the prior hard 1;500.
Narrative: Departing TEB on the RUUDY departure; the Captain was the non flying pilot in the right seat and I was the SIC/flying pilot; but sitting in the left seat. The Captain deplaned the passengers; handled the luggage and paid the applicable fees then returned to the plane while I received the PDC and set up the FMS for departure. The RUUDY SID has a final altitude of 2;000 (or as assigned) with an intermediate stop at 1;500 until crossing WENTZ. The Captain set 2;000 in the altitude preselect which should have been 1;500. He then briefed the clearance. As the flying pilot I considered the noise abatement for the Teterboro area and intended to climb as expeditiously as possible to the initial altitude. We discussed 1;500 at WENTZ then the climb to 2;000 over TASCA however I didn't catch that the Captain had set 2;000 in the altitude preselect. The chain of events was: 1. the incorrect setting of the altitude preselect; 2. preoccupation with noise abatement; 3. I followed the flight director to the preselected altitude. I should have been able to break the error chain simply by noting the incorrect setting of the initial altitude rather than trusting what was set to be correct.
Data retrieved from NASA's ASRS site as of July 2013 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.