Cirrus Vision pilot reported a runway incursion and a ground conflict with another aircraft that was on final approach that had to perform a go-around.

Date: 2025-04 · Aircraft: Cirrus Vision SF50 · Phase: takeoff

Anomalies: conflict-ground-conflict|critical|ground-incursion-runway

Synopsis

Cirrus Vision pilot reported a runway incursion and a ground conflict with another aircraft that was on final approach that had to perform a go-around.

Narrative

I was departing ZZZ on a clear day but flying on an IFR flight plan. I picked up my clearance on the ground while holding at the hold short line for the runway. I received a void time and quickly changed to unicom and heard no traffic. I announce my take off intentions; looked for approaching traffic; and seeing none; and taxied onto the runway and began my takeoff roll. I then heard an aircraft state that the aircraft on the run should expedite take off for traffic on short final. I was already at full takeoff power. The aircraft then said he was going around and asked if I heard him say abort takeoff. I replied that I thought he said expedite take off. He said 'Oh; well; another day at the office.' There was no more communication. I never saw the aircraft and do not know what type is was.Contributing to this mishap was my rush to meet the void time. Also; because I was on the ground clearance frequency; I did not hear any announcements of pattern traffic. I did look for traffic down the approach corridor but saw none. I probably rushed the scan for traffic trying to meet the void time.I will spend proper time and not rush clearing the approach corridor before taking a runway. I will pause and listen for pattern traffic longer. I will not rush just because of a void time.

Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.