<< >> NASA ASRS Report 538153, February 2002

A C210 pilot, taxiing for takeoff at fcm, misunderstood his clearance and taxied onto the active runway without a clearance.

Attributes
ACN	538153
Time
Date	200202
Day	Sun
Local Time Of Day	0601 To 1200
Place
Locale Reference	airport : fcm.airport
State Reference	MN
Altitude	agl single value : 0
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Operator	general aviation : personal
Make Model Name	Cessna 210 Centurion / Turbo Centurion 210C, 210D
Operating Under FAR Part	Part 91
Flight Phase	ground : taxi
Flight Plan	VFR
Person 1
Affiliation	other
Function	flight crew : single pilot
Qualification	pilot : commercial pilot : multi engine pilot : instrument
Experience	flight time last 90 days : 10 flight time total : 875 flight time type : 40
ASRS Report	538153
Person 2
Affiliation	government : faa
Function	controller : ground
Events
Anomaly	incursion : runway non adherence : published procedure non adherence : clearance non adherence : far
Independent Detector	other controllera
Resolutory Action	controller : issued new clearance none taken : detected after the fact
Consequence	faa : reviewed incident with flight crew
Supplementary
Problem Areas	Flight Crew Human Performance
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

I misunderstood a taxi clearance to mean taxi on a runway. There was no landing or departing traffic using the runway and no conflict. My taxi clearance was received just as a new ATIS was released. I was not aware the arrival and departure runway had also changed from runway 18 to runways 27L/27R. My taxi instructions were 'taxi runway 27R hold short runway 18.' takeoff and landing operations were still visible on runway 18. At this airport, when runways 18/36 is active, ground traffic is often directed along runway 27R to avoid conflicting taxi traffic. I have followed such clrncs several times before. I misunderstood 'taxi runway 27R' etc, to mean taxi along runway 27R, hold short of runway 18 and expect further clearance to the runway 18 run-up pad. As I approached the runways 27R/18 intersection, ground directed me to turn onto the parallel, cross runway 18 and taxi runway 27R. I realized the error at this point. Shortly afterward I was the first to depart on runway 27R.

Related reports:

• Flight crew misunderstood taxi clearance and continued taxii...
• Flight crew of A320 taxiing to runway 24L at lax misundersto...
• A C206 pilot, taxiing for takeoff at dec, misunderstood his ...

	Enter your search terms Submit search form
	Web www.37000feet.com

Original NASA ASRS Text

Title: A C210 PLT, TAXIING FOR TKOF AT FCM, MISUNDERSTOOD HIS CLRNC AND TAXIED ONTO THE ACTIVE RWY WITHOUT A CLRNC.

Narrative: I MISUNDERSTOOD A TAXI CLRNC TO MEAN TAXI ON A RWY. THERE WAS NO LNDG OR DEPARTING TFC USING THE RWY AND NO CONFLICT. MY TAXI CLRNC WAS RECEIVED JUST AS A NEW ATIS WAS RELEASED. I WAS NOT AWARE THE ARR AND DEP RWY HAD ALSO CHANGED FROM RWY 18 TO RWYS 27L/27R. MY TAXI INSTRUCTIONS WERE 'TAXI RWY 27R HOLD SHORT RWY 18.' TKOF AND LNDG OPS WERE STILL VISIBLE ON RWY 18. AT THIS ARPT, WHEN RWYS 18/36 IS ACTIVE, GND TFC IS OFTEN DIRECTED ALONG RWY 27R TO AVOID CONFLICTING TAXI TFC. I HAVE FOLLOWED SUCH CLRNCS SEVERAL TIMES BEFORE. I MISUNDERSTOOD 'TAXI RWY 27R' ETC, TO MEAN TAXI ALONG RWY 27R, HOLD SHORT OF RWY 18 AND EXPECT FURTHER CLRNC TO THE RWY 18 RUN-UP PAD. AS I APCHED THE RWYS 27R/18 INTXN, GND DIRECTED ME TO TURN ONTO THE PARALLEL, CROSS RWY 18 AND TAXI RWY 27R. I REALIZED THE ERROR AT THIS POINT. SHORTLY AFTERWARD I WAS THE FIRST TO DEPART ON RWY 27R.

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.