CL-30 Captain reported while on final another aircraft entered the runway for departure resulting in a go-around.
Synopsis
CL-30 Captain reported while on final another aircraft entered the runway for departure resulting in a go-around.
Narrative
On Day 0 we executed a go-around due to a C-172 pulling out on the Runway XX at ZZZ. We were on approximately a mile final at 300-400 feet. I (pilot in command (PIC)) was the pilot flying (PF); and I executed the go-around as soon as I saw the aircraft take the runway and begin his takeoff roll. During this procedure; I turned to join midfield cross wind early to avoid the departing Cessna from climbing into us (it was clear that he was not listening to radio calls or looking for area traffic). We then flew another left closed pattern; completed all necessary checklists; and made a successful landing without further disruption.Our lights were fully configured for landing; and we were making several radio calls to report our position - to include making a call approximately 2 miles before this go-around was executed.ASOS at the time was missing several elements of the weather and we needed to rely on ATC and ADS-B internet feeds to determine what runway was the active. Additionally; we did call the FBO while enroute and they also concluded that Runway XX was the preferred runway for area pilots. A discussion was had about Runway XY being slightly more preferable for our situation due to the slightly better LDA numbers; but after weighing all other risks of flying a pattern outside of the other GA (to include pilots not reporting positions on CTAF; not listening to CTAF; and/or possible collisions in-flight or during our landing roll); we decided there would be less risk in landing on Runway XX. There were no passengers on this flight as we were on a positioning flight to pick them up.Cause: The aircraft on the ground failed to monitor CTAF as well as failed to check that final was clear before taking the runway for takeoff.Suggestions: I've had several issues at this airport - all of which involves small GA aircraft's lack of awareness of much larger and much faster aircraft in their traffic pattern. In fact; I explained to my second in command (SIC) that I very much didn't enjoy operations at this airport due to the very reason that led us to go-around. Though I I know it's not an option; but I would recommend that we use ZZZ1 instead of ZZZ moving forward. The large amount of flight training and transient small GA aircraft simply makes this airport quite dangerous for larger and faster aircraft.
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.