Narrative:

The weather leaving ZZZ was clear and winds were calm. Other than a taxi instruction that was incorrect from ground control where the controller kept providing a taxi from the north ramp even though we requested taxi from FBO ramp; the taxi out to the runway was normal. Tower control took over the taxi instructions prior to crossing the landing runway of xxr and xxl while we were given instructions to taxi to runway xy. Runway xy was entered into the FMS (flight management system) with the departure. The takeoff briefing was performed as we taxied out identifying a long range nav takeoff and confirming the left nav selection on the guidance controller. The takeoff was normal at xa:45Z until around 500 ft. Above ground level; a wasp was seen coming out from the top of the glare-shield and landed on the hand of the pilot flying. It became apparent that the wasp was going to cause issues immediately.initial focus was to ensure aircraft was just flying but no attention was made to the flight director. We were still flying with wings somewhat level and nose high although later we realized we had turned slightly to the right. The control of the aircraft swapped back and forth from left to right-side pilot several times as the wasp kept flying around. The right-side pilot finally found a napkin in the cockpit to attempt to kill the wasp and transfer of control went back to the left-side pilot. Finally the wasp was trapped and focus was back to navigating versus just attitude flying. At that point; we noticed that the flight was not on course about the time that departure asked us our heading. I told them to standby as we finally killed the wasp under the napkin. We were given a heading of 330 which we then initiated only to be later told just to navigate back to the east toward ZZZ1. Moments later; we were informed that ATC wanted a phone call to which I replied that it would be quite some time before that could happen. What we did correctly [was] fly the aircraft. At no point in the takeoff and initial climb out did we lose control of the aircraft while attempting to find and kill our invading wasp. No other traffic was identified nor did the TCAS (traffic collision alerting system) alert us to that issue. What we did not do correctly [was] navigate. The crew kept having to juggle the wasp vs. The airplane in an attempt to not get stung. Not to be taken lightly given different weather and terrain conditions but this one is for the books and for training classes for sure.

Google
 

Original NASA ASRS Text

Title: Gulfstream IV flight crew reported a wasp was discovered in the cockpit after takeoff.

Narrative: The weather leaving ZZZ was clear and winds were calm. Other than a taxi instruction that was incorrect from Ground Control where the controller kept providing a taxi from the North Ramp even though we requested taxi from FBO ramp; the taxi out to the runway was normal. Tower Control took over the taxi instructions prior to crossing the landing Runway of XXR and XXL while we were given instructions to taxi to Runway XY. Runway XY was entered into the FMS (Flight Management System) with the departure. The takeoff briefing was performed as we taxied out identifying a Long Range Nav takeoff and confirming the L Nav selection on the guidance controller. The takeoff was normal at XA:45Z until around 500 ft. above ground level; a wasp was seen coming out from the top of the glare-shield and landed on the hand of the Pilot Flying. It became apparent that the wasp was going to cause issues immediately.Initial focus was to ensure aircraft was just flying but no attention was made to the flight director. We were still flying with wings somewhat level and nose high although later we realized we had turned slightly to the right. The control of the aircraft swapped back and forth from Left to Right-Side Pilot several times as the wasp kept flying around. The Right-Side Pilot finally found a napkin in the cockpit to attempt to kill the wasp and transfer of control went back to the Left-Side Pilot. Finally the wasp was trapped and focus was back to navigating versus just attitude flying. At that point; we noticed that the flight was not on course about the time that Departure asked us our heading. I told them to standby as we finally killed the wasp under the napkin. We were given a heading of 330 which we then initiated only to be later told just to navigate back to the east toward ZZZ1. Moments later; we were informed that ATC wanted a phone call to which I replied that it would be quite some time before that could happen. What we did correctly [was] fly the aircraft. At no point in the takeoff and initial climb out did we lose control of the aircraft while attempting to find and kill our invading wasp. No other traffic was identified nor did the TCAS (Traffic Collision Alerting System) alert us to that issue. What we did not do correctly [was] navigate. The crew kept having to juggle the wasp vs. the airplane in an attempt to not get stung. Not to be taken lightly given different weather and terrain conditions but this one is for the books and for training classes for sure.

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.