37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1477289 |
Time | |
Date | 201708 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | ZZZ.ARTCC |
State Reference | US |
Environment | |
Flight Conditions | VMC |
Aircraft 1 | |
Make Model Name | Gulfstream IV / G350 / G450 |
Operating Under FAR Part | Part 91 |
Flight Phase | Cruise |
Route In Use | Oceanic |
Flight Plan | IFR |
Person 1 | |
Function | Captain Pilot Flying |
Qualification | Flight Crew Multiengine Flight Crew Instrument Flight Crew Flight Instructor Flight Crew Air Transport Pilot (ATP) Flight Crew Flight Engineer |
Experience | Flight Crew Last 90 Days 60 Flight Crew Total 22000 Flight Crew Type 60 |
Events | |
Anomaly | Deviation - Procedural Published Material / Policy Deviation - Track / Heading All Types Flight Deck / Cabin / Aircraft Event Other / Unknown |
Narrative:
We received a SELCAL towards the end of our flight; requesting a position report. I'm not sure which way point after the fact as I now decided to fill out this report. No conflicts reported.we were maybe 5 or 10 minutes past the reporting point and within the 2 minutes of the previous report.we made the report immediately upon responding to the arinc request.it is worth looking at the circumstances. I was using a contract pilot; nfp (non flying pilot). There is a pilot shortage so this person was not my first choice. He has a history of sometimes; not always; difficult CRM; which is manifested by being defensive and sometimes not following SOP.problems began when he; rather than establishing enroute HF communications; made a report of a coast out position that was not requested; nor did he request a SELCAL check. This was a bit odd. When I asked him what he meant; he was defensive saying 'this was his standard procedure'. We eventually got the SELCAL check.he shortly after that entered the wrong altitude (no big deal) in the altitude prompter as 16000; when the controller had said 15000. I asked him to confirm the altitude with the controller; he did so but with some attitude. My request was kind and appropriate.he was somewhat silent after these two events.I later asked him to put on the cowl heat and he said; 'you do it'.I; without confrontation as the fp (flying pilot); put on the cowl heat.he later said 'I'm not your monkey' and that he didn't like when I asked him to do things that he thought I should do myself. Our SOP is to not have the fp pushing buttons when the nfp is free to do it.there was some tension for the remainder of the flight; which was already late; and this added to the exhaustion of both of us.this is why I think we flew past the waypoint; he the nfp missed it; and I did too.he is very competent in many ways; and that is why I continue to use him; (although his personality is challenging). Choosing contract pilots in this environment is kind of 'name your poison'. The best pilots are hired; the ones that are available; always have issues.my challenge is to work with the issues and prevent any confrontations in the cockpit. This was accomplished; but I have to walk gently with some personalities.I have a heightened awareness when working with a different pilot; and I have to re-triple my efforts.he called me three days later to apologize; which is what he always does. One would ask; why do I use him? He an otherwise nice person to be with on the road and he is very his honest about this 'issue' he is working on. We both try to work with it. He is mostly competent; which is better that some of the other choices I've had to work with.he is not the first or even second person I call; but he was the only one available. It is getting harder all the time to fill our temporary needs.on balance; the flight was conducted safely but I am reminded to pay extra attention to all of the details.
Original NASA ASRS Text
Title: Captain of a corporate turbojet reported issues with flying with contract pilots.
Narrative: We received a SELCAL towards the end of our flight; requesting a position report. I'm not sure which way point after the fact as I now decided to fill out this report. No conflicts reported.We were maybe 5 or 10 minutes past the reporting point and within the 2 minutes of the previous report.We made the report immediately upon responding to the ARINC request.It is worth looking at the circumstances. I was using a contract pilot; NFP (Non Flying Pilot). There is a pilot shortage so this person was not my first choice. He has a history of sometimes; not always; difficult CRM; which is manifested by being defensive and sometimes not following SOP.Problems began when he; rather than establishing enroute HF communications; made a report of a coast out position that was not requested; nor did he request a SELCAL check. This was a bit odd. When I asked him what he meant; he was defensive saying 'this was his standard procedure'. We eventually got the SELCAL check.He shortly after that entered the wrong altitude (no big deal) in the altitude prompter as 16000; when the controller had said 15000. I asked him to confirm the altitude with the controller; he did so but with some attitude. My request was kind and appropriate.He was somewhat silent after these two events.I later asked him to put on the COWL heat and he said; 'you do it'.I; without confrontation as the FP (Flying Pilot); put on the COWL heat.He later said 'I'm not your monkey' and that he didn't like when I asked him to do things that he thought I should do myself. Our SOP is to not have the FP pushing buttons when the NFP is free to do it.There was some tension for the remainder of the flight; which was already late; and this added to the exhaustion of both of us.This is why I think we flew past the waypoint; he the NFP missed it; and I did too.He is very competent in many ways; and that is why I continue to use him; (although his personality is challenging). Choosing contract pilots in this environment is kind of 'name your poison'. The best pilots are hired; the ones that are available; always have issues.My challenge is to work with the issues and prevent any confrontations in the cockpit. This was accomplished; but I have to walk gently with some personalities.I have a heightened awareness when working with a different pilot; and I have to re-TRIPLE my efforts.He called me three days later to apologize; which is what he always does. One would ask; why do I use him? He an otherwise nice person to be with on the road and he is very his honest about this 'issue' he is working on. We both try to work with it. He is mostly competent; which is better that some of the other choices I've had to work with.He is not the first or even second person I call; but he was the ONLY one available. It is getting harder all the time to fill our temporary needs.On balance; the flight was conducted safely but I am reminded to pay extra attention to all of the details.
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.