Narrative:

We were cleared for takeoff from runway 1. There was an aircraft holding short of runway 1 downfield at taxiway F. That aircraft had been stationary and holding short as we were taking the runway. After applying takeoff thrust and beginning our takeoff roll the other aircraft starting moving towards the runway. It appeared to me that they were attempted to cross runway 1 and I initiated an abort and a split second later the tower also told us to abort the takeoff. The abort occurred at less than 80 kts. As we were decelerating the other aircraft on taxiway F appeared to stop and never entered the runway area. We cleared runway 1 on to runway 4/22 and taxied back to the hold block. I contacted dispatch to inform them of the abort and revalidate the release. During that time the tower asked us to call them at our convenience. I spoke with the tower manager on duty and she informed me that the aircraft that attempted to cross the runway mistakenly read back a clearance for a different flight to cross runway 4. She informed us that we did nothing wrong and that they would be performing an investigation on their side. After revalidating we departed and the flight continued without incident. This was simply a read back error for another crew that could have resulted in a runway incursion. The only suggestion I would bring is to be certain the flight is operating under sterile cockpit procedures on the ground and if in doubt of a clearance to clarify before taking action on it. I'd also like to give accolades to both the tower and ground controllers for catching the other crew's error quickly and correcting the situation in such a timely fashion.

Related reports:

Google
 

Original NASA ASRS Text

Title: After commencing takeoff roll; CRJ-200 crew noticed an aircraft about to enter the runway and rejected the takeoff.

Narrative: We were cleared for takeoff from Runway 1. There was an aircraft holding short of Runway 1 downfield at Taxiway F. That aircraft had been stationary and holding short as we were taking the runway. After applying takeoff thrust and beginning our takeoff roll the other aircraft starting moving towards the runway. It appeared to me that they were attempted to cross Runway 1 and I initiated an abort and a split second later the Tower also told us to abort the takeoff. The abort occurred at less than 80 kts. As we were decelerating the other aircraft on Taxiway F appeared to stop and never entered the runway area. We cleared Runway 1 on to Runway 4/22 and taxied back to the hold block. I contacted Dispatch to inform them of the abort and revalidate the release. During that time the Tower asked us to call them at our convenience. I spoke with the Tower Manager on duty and she informed me that the aircraft that attempted to cross the runway mistakenly read back a clearance for a different flight to cross Runway 4. She informed us that we did nothing wrong and that they would be performing an investigation on their side. After revalidating we departed and the flight continued without incident. This was simply a read back error for another crew that could have resulted in a runway incursion. The only suggestion I would bring is to be certain the flight is operating under sterile cockpit procedures on the ground and if in doubt of a clearance to clarify before taking action on it. I'd also like to give accolades to both the Tower and Ground controllers for catching the other crew's error quickly and correcting the situation in such a timely fashion.

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.