A B737-300 rejects takeoff on dtw runway 22L because an aircraft on taxiway Q appeared to be crossin...

Attributes
ACN	670220
Time
Date	200509
Local Time Of Day	1801 To 2400
Place
Locale Reference	airport : dtw.airport
State Reference	MI
Altitude	agl single value : 0
Environment
Flight Conditions	VMC
Light	Night
Aircraft 1
Operator	common carrier : air carrier
Make Model Name	B737-300
Operating Under FAR Part	Part 121
Flight Phase	ground : takeoff roll
Flight Plan	IFR
Aircraft 2
Controlling Facilities	tower : dtw.tower
Make Model Name	Any Unknown or Unlisted Aircraft Manufacturer
Flight Phase	ground : taxi
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Experience	flight time last 90 days : 60 flight time total : 12000 flight time type : 5000
ASRS Report	670220
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Events
Anomaly	other anomaly other
Independent Detector	other flight crewa
Resolutory Action	flight crew : rejected takeoff
Consequence	faa : reviewed incident with flight crew
Supplementary
Problem Areas	Environmental Factor FAA ATC Human Performance Airport
Primary Problem	Airport

Narrative:

We had been cleared for takeoff on runway 22L in dtw. It was dark and I observed an aircraft that appeared to cross our runway. We had just set takeoff power and I elected to abort. We informed the tower and the controller informed us that the aircraft crossing was on taxiway Q south of runway 22L. When we cleared the runway; the controller's comment was; 'you are not the first to abort for this reason.' our speed was very low and was not a problem. I can see the potential problem during a high speed abort due to the unique situation at runway 22L and taxiway Q. I think the controller should inform the departing aircraft on runway 22L if an aircraft will be taxiing across on taxiway Q; or hold the crossing aircraft. Especially at night when you have no way of telling if an aircraft is actually crossing the runway or if it's on taxiway Q.

Original NASA ASRS Text

Title: A B737-300 REJECTS TKOF ON DTW RWY 22L BECAUSE AN ACFT ON TXWY Q APPEARED TO BE CROSSING THE RWY.

Narrative: WE HAD BEEN CLRED FOR TKOF ON RWY 22L IN DTW. IT WAS DARK AND I OBSERVED AN ACFT THAT APPEARED TO CROSS OUR RWY. WE HAD JUST SET TKOF POWER AND I ELECTED TO ABORT. WE INFORMED THE TWR AND THE CTLR INFORMED US THAT THE ACFT CROSSING WAS ON TXWY Q S OF RWY 22L. WHEN WE CLRED THE RWY; THE CTLR'S COMMENT WAS; 'YOU ARE NOT THE FIRST TO ABORT FOR THIS REASON.' OUR SPD WAS VERY LOW AND WAS NOT A PROB. I CAN SEE THE POTENTIAL PROB DURING A HIGH SPD ABORT DUE TO THE UNIQUE SIT AT RWY 22L AND TXWY Q. I THINK THE CTLR SHOULD INFORM THE DEPARTING ACFT ON RWY 22L IF AN ACFT WILL BE TAXIING ACROSS ON TXWY Q; OR HOLD THE CROSSING ACFT. ESPECIALLY AT NIGHT WHEN YOU HAVE NO WAY OF TELLING IF AN ACFT IS ACTUALLY CROSSING THE RWY OR IF IT'S ON TXWY Q.

Data retrieved from NASA's ASRS site as of January 2009 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.

A B737-300 rejects takeoff on dtw runway 22L because an aircraft on taxiway Q appeared to be crossing the runway.