 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Da-2000 flight crew reported the FMC depicted a course direct to an intersection resulting in a track deviation during departure.
| Attributes | |
| ACN | 1466073 |
| Time | |
| Date | 201707 |
| Local Time Of Day | 0601-1200 |
| Place | |
| Locale Reference | SCT.TRACON |
| State Reference | CA |
| Environment | |
| Light | Daylight |
| Aircraft 1 | |
| Make Model Name | Falcon 2000 |
| Flight Phase | Climb |
| Route In Use | SID HARYS1 |
| Flight Plan | IFR |
| Component | |
| Aircraft Component | FMS/FMC |
| Person 1 | |
| Function | First Officer Pilot Not Flying |
| Qualification | Flight Crew Air Transport Pilot (ATP) |
| Person 2 | |
| Function | Pilot Flying Captain |
| Events | |
| Anomaly | Aircraft Equipment Problem Less Severe Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy Deviation - Track / Heading All Types |
Narrative:
Cleared HARYS1 SID; climb via the SID except maintain 4000'. Sid calls for a turn to 110 and essentially radar vectors after. FMS was verified before taxi after takeoff during cruise; that the correct departure procedure was loaded with correct transition. When we were cleared for takeoff; I believe the scoreboard was set to rol with vpitch. Take off was normal. During flap retraction altitude (fra); I retracted the flaps when commanded by the captain and made the initial call to departure control. The ATC controller queried us on our direction. I looked down at our heading and noticed we were past the 110 heading and saw the captain correcting to the correct course. Somehow the command bars were commanding a intercept to bshow. I'm am totally perplexed on how the command bars would command a intercept to bshow when neither of us told it to do so. From what my understanding of the FMS and command bars are; it should have directed the airplane to the 110 heading and stopped. ATC then advised us to turn to a 120 heading. ATC advised us that a pilot deviation report will most likely be filed. Need to stay more vigilant on automation/flight director. Need to intervene sooner if the automation is not doing what we expect it to do.
Original NASA ASRS Text
Title: DA-2000 flight crew reported the FMC depicted a course direct to an intersection resulting in a track deviation during departure.
Narrative: Cleared HARYS1 SID; climb via the SID except maintain 4000'. Sid calls for a turn to 110 and essentially radar vectors after. FMS was verified before taxi after takeoff during cruise; that the correct Departure Procedure was loaded with correct transition. When we were cleared for takeoff; I believe the scoreboard was set to ROL with Vpitch. Take off was normal. During Flap Retraction Altitude (FRA); I retracted the flaps when commanded by the Captain and made the initial call to departure control. The ATC controller queried us on our direction. I looked down at our heading and noticed we were past the 110 heading and saw the Captain correcting to the correct course. Somehow the command bars were commanding a intercept to BSHOW. I'm am totally perplexed on how the command bars would command a intercept to BSHOW when neither of us told it to do so. From what my understanding of the FMS and command bars are; It should have directed the airplane to the 110 heading and stopped. ATC then advised us to turn to a 120 heading. ATC advised us that a pilot deviation report will most likely be filed. Need to stay more vigilant on automation/flight director. Need to intervene sooner if the automation is not doing what we expect it to do.
Data retrieved from NASA's ASRS site 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.