 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
A flight crew; new to their C560XLS+; failed to comply with the required track; altitudes; and speeds while flying the ruudy RNAV SID from teb.
| Attributes | |
| ACN | 1008036 |
| Time | |
| Date | 201205 |
| Local Time Of Day | 0001-0600 |
| Place | |
| Locale Reference | TEB.Airport |
| State Reference | NJ |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Make Model Name | Citation Excel (C560XL) |
| Operating Under FAR Part | Part 91 |
| Flight Phase | Initial Climb |
| Route In Use | SID RUUDY4 |
| Flight Plan | IFR |
| Component | |
| Aircraft Component | FMS/FMC |
| Person 1 | |
| Function | Captain Pilot Flying |
| Qualification | Flight Crew Flight Instructor Flight Crew Instrument Flight Crew Multiengine Flight Crew Air Transport Pilot (ATP) |
| Experience | Flight Crew Last 90 Days 60 Flight Crew Total 5100 Flight Crew Type 500 |
| Events | |
| Anomaly | Aircraft Equipment Problem Less Severe Deviation - Altitude Crossing Restriction Not Met Deviation - Procedural Published Material / Policy Deviation - Procedural Clearance Deviation - Speed All Types Deviation - Track / Heading All Types |
Narrative:
We were departing on the ruudy RNAV SID from teb. Our company recently bought an xls+ and we are still learning our new avionics. The FMS was programmed and showed the SID accurately with all altitudes. After takeoff however; the FMS cycled from the first 'intercept' waypoint on the departure procedure to the second fix; wentz. The aircraft had not traveled the 2.3 miles; but only a few tenths. In attempting to get the aircraft towards the intercept fix; we exceeded the 250 KT limit below class B airspace; and also missed the 2;000 ft limitation at tasca by approximately 200 ft; climbing through at roughly 1;800 ft.with a new aircraft there are usually some bugs to work out. In hindsight; I probably should have selected heading and continued to a point that would have been 2.3 miles from the departure end of the runway and then continued to wentz. Doing so instead of trying to re-initialize the FMS to the proper 'intercept' waypoint would have eliminated the speed and altitude deviation at the next fix; as we would not then have been fixated on the route so much.I will be looking again at the departure procedure with the FMS at my next training event in the simulator.
Original NASA ASRS Text
Title: A flight crew; new to their C560XLS+; failed to comply with the required track; altitudes; and speeds while flying the RUUDY RNAV SID from TEB.
Narrative: We were departing on the RUUDY RNAV SID from TEB. Our company recently bought an XLS+ and we are still learning our new avionics. The FMS was programmed and showed the SID accurately with all altitudes. After takeoff however; the FMS cycled from the first 'intercept' waypoint on the departure procedure to the second fix; WENTZ. The aircraft had not traveled the 2.3 miles; but only a few tenths. In attempting to get the aircraft towards the intercept fix; we exceeded the 250 KT limit below Class B Airspace; and also missed the 2;000 FT limitation at TASCA by approximately 200 FT; climbing through at roughly 1;800 FT.With a new aircraft there are usually some bugs to work out. In hindsight; I probably should have selected HDG and continued to a point that would have been 2.3 miles from the departure end of the runway and then continued to WENTZ. Doing so instead of trying to re-initialize the FMS to the proper 'intercept' waypoint would have eliminated the speed and altitude deviation at the next fix; as we would not then have been fixated on the route so much.I will be looking again at the departure procedure with the FMS at my next training event in the simulator.
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.