DHC8 flight crew request takeoff clearance air traffic area mfr. Hearing cleared for takeoff, taxied onto runway, and were challenged by local controller due to wrong call sign.

Home

Browse by month

Random

Latest

About

Contact

Attributes
ACN	577968
Time
Date	200303
Day	Fri
Local Time Of Day	0601 To 1200
Place
Locale Reference	airport : mfr.airport
State Reference	OR
Altitude	agl single value : 0
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Operator	common carrier : air carrier
Make Model Name	Dash 8-200
Operating Under FAR Part	Part 121
Flight Phase	ground : position and hold ground : taxi ground : takeoff roll
Flight Plan	IFR
Aircraft 2
Controlling Facilities	tower : mfr.tower
Operator	common carrier : air carrier
Make Model Name	Commercial Fixed Wing
Operating Under FAR Part	Part 121
Flight Phase	ground : takeoff roll ground : position and hold
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : multi engine pilot : instrument pilot : commercial pilot : cfi
Experience	flight time last 90 days : 200 flight time total : 1300 flight time type : 470
ASRS Report	577968
Person 2
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Events
Anomaly	conflict : ground less severe incursion : runway non adherence : clearance other anomaly other
Independent Detector	other controllera
Resolutory Action	controller : issued new clearance controller : issued advisory flight crew : became reoriented flight crew : rejected takeoff
Consequence	faa : reviewed incident with flight crew
Supplementary
Problem Areas	Flight Crew Human Performance ATC Human Performance Environmental Factor
Primary Problem	Flight Crew Human Performance

Narrative:

I was the first officer on flight from mfr. Our call sign was abc. While we were taxiing to runway 32, medford tower cleared us for takeoff. The captain responded with 'cleared for takeoff aircraft X.' we taxied onto the runway, and as we lined up with the centerline, medford tower informed us we were not cleared for takeoff. We came to a stop. The captain said he thought we were cleared for takeoff. Tower said there might have been confusion, because he cleared aircraft with call sign air data computer for takeoff. The captain told tower he did read back the takeoff clearance. We were cleared for takeoff. Handed off to departure, and there were no further comments about the situation from ATC. I believe this was an understandable mistake on our behalf due to the similar sounding call signs, and that the tower controller should have caught our mistake during readback.

Original NASA ASRS Text

Title: DHC8 FLT CREW REQUEST TKOF CLRNC ATA MFR. HEARING CLRED FOR TKOF, TAXIED ONTO RWY, AND WERE CHALLENGED BY LCL CTLR DUE TO WRONG CALL SIGN.

Narrative: I WAS THE FO ON FLT FROM MFR. OUR CALL SIGN WAS ABC. WHILE WE WERE TAXIING TO RWY 32, MEDFORD TWR CLRED US FOR TKOF. THE CAPT RESPONDED WITH 'CLRED FOR TKOF ACFT X.' WE TAXIED ONTO THE RWY, AND AS WE LINED UP WITH THE CTRLINE, MEDFORD TWR INFORMED US WE WERE NOT CLRED FOR TKOF. WE CAME TO A STOP. THE CAPT SAID HE THOUGHT WE WERE CLRED FOR TKOF. TWR SAID THERE MIGHT HAVE BEEN CONFUSION, BECAUSE HE CLRED ACFT WITH CALL SIGN ADC FOR TKOF. THE CAPT TOLD TWR HE DID READ BACK THE TKOF CLRNC. WE WERE CLRED FOR TKOF. HANDED OFF TO DEP, AND THERE WERE NO FURTHER COMMENTS ABOUT THE SIT FROM ATC. I BELIEVE THIS WAS AN UNDERSTANDABLE MISTAKE ON OUR BEHALF DUE TO THE SIMILAR SOUNDING CALL SIGNS, AND THAT THE TWR CTLR SHOULD HAVE CAUGHT OUR MISTAKE DURING READBACK.

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