CRJ-200 flight crew reported rejected takeoff due to GA aircraft incursion on runway at a non-towered airport.
Synopsis
CRJ-200 flight crew reported rejected takeoff due to GA aircraft incursion on runway at a non-towered airport.
Narrative
The day was made up of weight and balance issues; flight crew swaps; and weather delays. Weather in ZZZ was poor due to the marine layer and fog over the airport. Visibility was restricted and was a typical IFR weather day. We waited behind another preceding aircraft both awaiting IFR release from the uncontrolled field. We made position reports over the common traffic advisory frequency stating we were taxiing and holding short of Runway XX number two behind the other departing aircraft. Upon getting our IFR release we made a report we were departing from Runway XX on the common traffic advisory frequency and lined up on the runway. We had completed all required checks and checklists as well. Once on the runway visibility was poor as such was the IFR day and we advanced the thrust levers and began our takeoff. At that moment a Cirrus aircraft stated they were crossing Runway XX. This was the first call we heard them say and I was unaware there was even a Cirrus on the field at the time. We reached about 60 kts. and aborted our takeoff and stated on the frequency that we were aborting. The Cirrus pilot was over the hold short bars and we came to a stop 150 ft. from them. We taxied off set brakes; checked in with the flight attendant; and called the Duty Manager. Contributing factors: IFR weather on the field and restricted visibility. Airport was a non-towered airport. Other air traffic in the area on the field failed to make position reports.It is important to make position reports at a non-towered airport and extremely important to do so under IFR low visibility operations. We had done everything as normal per the operation and unfortunately had this event occur due to the lack of awareness and lack of reporting from the preceding Cirrus aircraft.
Second reporter narrative
Day started with weight and balance issues from our report time. From ZZZ2 to ZZZ we dealt with similar weight and balance issues; crew member swap and weather in ZZZ. Once all three issues were dealt with the flight continued to ZZZ. ZZZ to ZZZ1 weather was IFR on field and there is no tower at ZZZ. We were positioned number 2 for takeoff behind another commercial carrier and were making position reports on CTAF. The proceeding commercial carrier took off before us and we were released on our IFR flight plan from ZZZ to ZZZ1 with ZZZ Center. We completed the remaining checklists made a position report stating we were taking Runway XX. At 60 kts. the takeoff was aborted due to a Cirrus who's only radio transmission was 'cirrus crossing Runway XX'. We stopped at taxiway delta and saw the cirrus crossing the runway was at Taxiway X (roughly 150 ft. from the other aircraft) about a cowling width into the takeoff Runway XX. We then proceeded to taxi off the runway onto Taxiway Y where we verified the flight attendant and her cabin were safe and secure. Called the Duty Manager; Dispatch and then proceeded to ZZZ1. Contributing factors were the weather in ZZZ being IFR at the time of our departure. ZZZ being a non-towered airport; and failure of other traffic in the area to not make position reports. I believe that in this situation there is nothing more that can be accomplished in order to prevent this type of incursion. When there are commercial IFR operations in use there are SOP's that must be followed; and even with position reports and clearing the area ahead etc.; if there are others not making radio calls of their intentions; position etc. or in this case making a radio call as thCRJ-200ey were crossing an active runway this type of incursion will happen. You cannot put an SOP for what others may do at an untowered airport
More incidents for this aircraft family →
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.