Narrative:

Departed ZZZ for ZZZ1 for repositioning. After takeoff on initial climb; the terrain alert sounds 'loudly'. 'Terrain' 'pull up' 'pull up'. This was a surprise and a distraction; I was told to climb to 2500/heading 140. I had the autopilot on and engage and all instruments were reading accurately. However it was disturbing to be in IMC/dark and getting this type of alert. Flying the plane first; I was unable to switch to departure in a timely manner; and dealing with this alert; I passed my altitude and continued climbing; as she keep saying pull up. I was finally able to contact departure who was aware I was having trouble; as I told departure tower-to let them know I was having trouble and unable to call at this moment. Settled level 4000 and still on assigned heading; and all was fine again. No more alerts; until descent into my destination airport. It started again descending through 3000. As I was confident in the instruments I ignored the alerts; but it was still a distraction. After landing; and calling field service; we discovered it was not the plane at all! It was my device that had an efb garmin pilot; that was bluetooth to my headset that was giving me the alerts. My lesson: pilots need to verify that portable efbs that are bluetooth connected to headsets are properly workings or not turned on. Although I regret passing my assigned altitude; and delaying my contact to departure. My #1 priority was to fly the plane; and talk later. I was able to do this. I will however; always check my portable efb and turn it off when not using it. I hope this lesson will help other pilots.

Google
 

Original NASA ASRS Text

Title: SF50 Pilot reported erroneous terrain alert on departure due to improperly configured portable EFB resulting in altitude clearance deviation.

Narrative: Departed ZZZ for ZZZ1 for repositioning. After takeoff on initial climb; the terrain alert sounds 'loudly'. 'TERRAIN' 'PULL UP' 'PULL UP'. This was a surprise and a distraction; I was told to climb to 2500/Heading 140. I had the autopilot on and engage and all instruments were reading accurately. However it was disturbing to be in IMC/Dark and getting this type of alert. Flying the Plane first; I was unable to switch to Departure in a timely manner; and dealing with this alert; I passed my altitude and continued climbing; as she keep saying pull up. I was finally able to contact Departure who was aware I was having trouble; as I told Departure Tower-to let them know I was having trouble and unable to call at this moment. Settled level 4000 and still on assigned heading; and all was fine again. No more alerts; until descent into my destination airport. It started again descending through 3000. As I was confident in the instruments I ignored the alerts; but it was still a distraction. After landing; and calling Field Service; we discovered it was not the plane at all! It was my device that had an EFB Garmin Pilot; that was bluetooth to my headset that was giving me the alerts. My lesson: Pilots need to verify that portable EFBs that are bluetooth connected to headsets are properly workings or not turned on. Although I regret passing my assigned altitude; and delaying my contact to Departure. My #1 priority was to fly the plane; and talk later. I was able to do this. I will however; always check my portable EFB and turn it off when not using it. I hope this lesson will help other pilots.

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.