37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 912400 |
Time | |
Date | 201009 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | TEB.Airport |
State Reference | NJ |
Environment | |
Flight Conditions | IMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Light Transport Low Wing 2 Turbojet Eng |
Operating Under FAR Part | Part 91 |
Flight Phase | Initial Climb |
Route In Use | SID RUUDY TWO |
Component | |
Aircraft Component | FMS/FMC |
Person 1 | |
Function | Pilot Flying Captain |
Qualification | Flight Crew Flight Instructor Flight Crew Air Transport Pilot (ATP) Flight Crew Instrument Flight Crew Multiengine |
Experience | Flight Crew Last 90 Days 100 Flight Crew Total 12500 Flight Crew Type 1500 |
Events | |
Anomaly | Deviation - Procedural Published Material / Policy Deviation - Procedural Clearance Deviation - Track / Heading All Types Inflight Event / Encounter Weather / Turbulence |
Narrative:
Departed teb on ruudy two SID. As this was the first time for me; I studied it before departure. I wasn't exactly sure if the FMS would head 240 degrees to intercept 260 degree track to ruudy or not or if I had to do any action. Please understand the weather was truly terrible. Thunderstorm had joined with a fairly strong fall cold front bringing rain and wind to new york area. We took off with 25 KTS gusting to 37 KTS. As this was a strong crosswind; the heading track to ruudy was strange to say the least. Well; at ruudy the FMS CDI swung around to a 160 degree turn; i.e.; I almost made a u-turn. I knew this couldn't be right so I just selected the dto function to brezy; the next fix. I turned to brezy and was stabilized on course for 2 minutes or so when approach told me I should have been heading 280 degrees from ruudy not brezy. I missed that on the chart. He was right. In writing this; it sounds like I'm an idiot; but in this weather and in this crowded; difficult airspace (that I am not all familiar with); I wonder if any one else could have done better. Lesson learned: I should have used the autopilot earlier in the flight.
Original NASA ASRS Text
Title: A high performance corporate jet Captain departed on the TEB RUUDY TWO departure and because of a high cross wind track deviation lost situational awareness and then the FMS apparently did not track accurately. The reporter pickup an inaccurate heading and had to be corrected by ATC.
Narrative: Departed TEB on RUUDY TWO SID. As this was the first time for me; I studied it before departure. I wasn't exactly sure if the FMS would head 240 degrees to intercept 260 degree track to RUUDY or not or if I had to do any action. Please understand the weather was truly terrible. Thunderstorm had joined with a fairly strong fall cold front bringing rain and wind to New York area. We took off with 25 KTS gusting to 37 KTS. As this was a strong crosswind; the heading track to RUUDY was strange to say the least. Well; at RUUDY the FMS CDI swung around to a 160 degree turn; i.e.; I almost made a U-turn. I knew this couldn't be right so I just selected the DTO function to BREZY; the next fix. I turned to BREZY and was stabilized on course for 2 minutes or so when Approach told me I should have been heading 280 degrees from RUUDY not BREZY. I missed that on the chart. He was right. In writing this; it sounds like I'm an idiot; but in this weather and in this crowded; difficult airspace (that I am not all familiar with); I wonder if any one else could have done better. Lesson learned: I should have used the autopilot earlier in the flight.
Data retrieved from NASA's ASRS site as of April 2012 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.