 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
A HS125 pilot was admonished by ATC for starting to climb to 2;000 ft just prior to wentz on the ruudy 4 departure from teb.
| Attributes | |
| ACN | 989759 |
| Time | |
| Date | 201201 |
| Local Time Of Day | 1201-1800 |
| Place | |
| Locale Reference | TEB.Airport |
| State Reference | NJ |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Make Model Name | BAe 125 Series 800 |
| Operating Under FAR Part | Part 91 |
| Flight Phase | Climb |
| Person 1 | |
| Function | Pilot Flying First Officer |
| Qualification | Flight Crew Air Transport Pilot (ATP) |
| Events | |
| Anomaly | Deviation - Altitude Crossing Restriction Not Met Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy |
Narrative:
[We were on the] ruudy 4 RNAV departure out of teb runway 24 to cross wentz at 1;500; then cross tasca at 2;000. We cross wentz at 1;500 and than started our climb to 2;000 just passing wentz. Teb departure called and gave us a new heading and a higher altitude and said we started our climb to 2;000 just before crossing wentz and then gave us a frequency change. Not sure what caused the problem. We know the problem with the newark arrivals descending over teterboro airport. As this is a RNAV departure; we have no other way on this SID to identify wentz; tasca and ruudy waypoints. We briefed for the departure; setting up the FMS for this SID and using VNAV. I was hand flying the airplane and at 1;500 noticed that the flight director was still calling for a climb. At wentz we then started our climb to 2;000. What could have caused the problem? VNAV not selected on the flight director or VNAV drop off after takeoff? We seldom do VNAV departures and in the future need to verify VNAV is selected.
Original NASA ASRS Text
Title: A HS125 pilot was admonished by ATC for starting to climb to 2;000 FT just prior to WENTZ on the RUUDY 4 departure from TEB.
Narrative: [We were on the] RUUDY 4 RNAV departure out of TEB Runway 24 to cross WENTZ at 1;500; then cross TASCA at 2;000. We cross WENTZ at 1;500 and than started our climb to 2;000 just passing WENTZ. TEB Departure called and gave us a new heading and a higher altitude and said we started our climb to 2;000 just before crossing WENTZ and then gave us a frequency change. Not sure what caused the problem. We know the problem with the Newark arrivals descending over Teterboro Airport. As this is a RNAV departure; we have no other way on this SID to identify WENTZ; TASCA and RUUDY waypoints. We briefed for the departure; setting up the FMS for this SID and using VNAV. I was hand flying the airplane and at 1;500 noticed that the flight director was still calling for a climb. At WENTZ we then started our climb to 2;000. What could have caused the problem? VNAV not selected on the flight director or VNAV drop off after takeoff? We seldom do VNAV departures and in the future need to verify VNAV is selected.
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.