![]() |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
| Attributes | |
| ACN | 1740411 |
| Time | |
| Date | 202004 |
| Local Time Of Day | 0601-1200 |
| Place | |
| Locale Reference | ZZZ.Airport |
| State Reference | US |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Make Model Name | Any Unknown or Unlisted Aircraft Manufacturer |
| Operating Under FAR Part | Part 91 |
| Flight Phase | Climb |
| Route In Use | Direct |
| Flight Plan | IFR |
| Person 1 | |
| Function | Pilot Flying |
| Qualification | Flight Crew Air Transport Pilot (ATP) Flight Crew Multiengine Flight Crew Instrument |
| Experience | Flight Crew Last 90 Days 30 Flight Crew Total 7500 Flight Crew Type 700 |
| Events | |
| Anomaly | Deviation - Procedural Clearance Deviation - Track / Heading All Types |
Narrative:
We were being vectored during the climb with a couple of different assigned headings. We were advised by ATC that we would be cleared to our destination in approximately 5 minutes. We were then cleared to our destination. I entered a direct in the GPS and selected navigation mode. We turned towards our destination; but were not going direct to it. The controller asked us if we were going direct to our destination right after we discovered we were not. We were already in a turn to the left heading direct to the destination. There were no conflicts or other aircraft that showed up on our TCAS. The problem arose as my normal co-pilot was out sick in quarantine for potential coronavirus and I had an inexperienced co-pilot. In addition to flying the aircraft; I was monitoring the new co-pilot as he was unsure of himself in this aircraft. We completed a 20 degree turn; so we were flying direct to our destination. The co-pilot's inexperience contributed to this event. Also contributing to the event was a 125 knot crosswind that made the track less intuitive.
Original NASA ASRS Text
Title: Pilot reported experiencing a track/heading deviation. Pilot stated the deviation occurred in part due to flying with an inexperienced co-pilot.
Narrative: We were being vectored during the climb with a couple of different assigned headings. We were advised by ATC that we would be cleared to our destination in approximately 5 minutes. We were then cleared to our destination. I entered a direct in the GPS and selected NAV Mode. We turned towards our destination; but were not going direct to it. The Controller asked us if we were going direct to our destination right after we discovered we were not. We were already in a turn to the left heading direct to the destination. There were no conflicts or other aircraft that showed up on our TCAS. The problem arose as my normal co-pilot was out sick in quarantine for potential Coronavirus and I had an inexperienced co-pilot. In addition to flying the aircraft; I was monitoring the new co-pilot as he was unsure of himself in this aircraft. We completed a 20 degree turn; so we were flying direct to our destination. The co-pilot's inexperience contributed to this event. Also contributing to the event was a 125 knot crosswind that made the track less intuitive.
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.