37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1050752 |
Time | |
Date | 201211 |
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 | Citation V/Ultra/Encore (C560) |
Operating Under FAR Part | Part 135 |
Flight Phase | Initial Climb |
Route In Use | SID RUUDY 4 |
Flight Plan | IFR |
Component | |
Aircraft Component | FMS/FMC |
Person 1 | |
Function | Captain Pilot Flying |
Qualification | Flight Crew Multiengine Flight Crew Air Transport Pilot (ATP) Flight Crew Flight Instructor |
Experience | Flight Crew Last 90 Days 100 Flight Crew Total 6300 Flight Crew Type 300 |
Events | |
Anomaly | Deviation - Procedural Published Material / Policy Deviation - Procedural Clearance Deviation - Track / Heading All Types |
Narrative:
I looked over the departure (ruudy 4 at teb) prior to my passenger's arrival. My co-pilot and I briefed the departure prior to taxi out and further discussed it on the taxi. It being a clear day; I said that we'd use navigation and possibly VNAV setting for takeoff. The VNAV was an experiment; since I knew of the 1;500 ft crossing at wentz and the 2;000 ft crossing at tasca and I wanted to see what the system would do. My thoughts were entirely on the crossing altitudes and not on the 'visual' map in my head. I was going to follow the navigation; which was obvious; but I was more concerned about the altitudes. When my co-pilot armed the system before takeoff; I should have realized there was a problem because the v-bars showed level with the horizon. He armed it as we were rolling onto the runway (no time to double-check; right). I knew my altitudes; so I thought it wasn't necessary to double-check the system. It was a normal takeoff; normal rotation; but after leaving the ground; the v-bars showed a left turn - and at 400 ft; I followed them. We were at about 210 degrees and in a left turn when tower controller said that we were supposed to be in a right turn and to turn to 260 degrees. He also said we were on an IFR flight plan and should be on that heading. (Yes; I agree.) I immediately corrected. The rest of the departure went normally. My altitudes were of no issue but the navigation was completely wrong just after takeoff. We disengaged the navigation and I flew it like I knew it. No further issues occurred and I heard nothing beyond this. We have no explanation for why the navigation system indicated a left turn; instead of the headings provided on the ruudy 4. The box showed everything correctly. The v-bars did not. Long story short: I put too much faith in my navigation on my airplane. I know better than that.
Original NASA ASRS Text
Title: A CE560 Captain flew the TEB RUUDY 4 with the VNAV engaged as an experiment and; after following the left turn guidance; was directed right by ATC to return to the departure track.
Narrative: I looked over the departure (RUUDY 4 at TEB) prior to my passenger's arrival. My co-pilot and I briefed the departure prior to taxi out and further discussed it on the taxi. It being a clear day; I said that we'd use NAV and possibly VNAV setting for takeoff. The VNAV was an experiment; since I knew of the 1;500 FT crossing at WENTZ and the 2;000 FT crossing at TASCA and I wanted to see what the system would do. My thoughts were entirely on the crossing altitudes and not on the 'visual' map in my head. I was going to follow the navigation; which was obvious; but I was more concerned about the altitudes. When my co-pilot armed the system before takeoff; I should have realized there was a problem because the v-bars showed level with the horizon. He armed it as we were rolling onto the runway (no time to double-check; right). I knew my altitudes; so I thought it wasn't necessary to double-check the system. It was a normal takeoff; normal rotation; but after leaving the ground; the v-bars showed a left turn - and at 400 FT; I followed them. We were at about 210 degrees and in a left turn when Tower Controller said that we were supposed to be in a right turn and to turn to 260 degrees. He also said we were on an IFR flight plan and should be on that heading. (Yes; I agree.) I immediately corrected. The rest of the departure went normally. My altitudes were of no issue but the navigation was completely wrong just after takeoff. We disengaged the navigation and I flew it like I knew it. No further issues occurred and I heard nothing beyond this. We have no explanation for why the navigation system indicated a left turn; instead of the headings provided on the RUUDY 4. The box showed everything correctly. The v-bars did not. Long story short: I put too much faith in my NAV on my airplane. I know better than that.
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.