Runway incursion by a C172 CFI pilot when he does not associate taxi clearance with new taxiway at i...

Attributes
ACN	571659
Time
Date	200301
Day	Sun
Local Time Of Day	0601 To 1200
Place
Locale Reference	airport : ict.airport
State Reference	KS
Altitude	agl single value : 0
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tower : sdf.tower
Operator	general aviation : personal
Make Model Name	Skyhawk 172/Cutlass 172
Operating Under FAR Part	Part 91
Flight Phase	ground : taxi
Flight Plan	IFR
Person 1
Affiliation	other
Function	flight crew : single pilot
Qualification	pilot : multi engine pilot : atp pilot : cfi
Experience	flight time last 90 days : 80 flight time total : 18900 flight time type : 10000
ASRS Report	571659
Person 2
Affiliation	government : faa
Function	controller : local controller : combined ground
Events
Anomaly	incursion : runway non adherence : clearance non adherence : far other anomaly other
Independent Detector	other controllera
Resolutory Action	none taken : detected after the fact
Supplementary
Problem Areas	Flight Crew Human Performance ATC Human Performance Airport
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

My home base airport has 3 runways with 2 parallel runways, runway 1R-19L and runway 1L-19R. For about 6 months, the east runway, runway 1R-19L, has been opened and closed to allow a new taxiway to be constructed on the east side of this runway. The incident happened on a sunday morning, so traffic was rather light and the ground and tower position were combined on the tower frequency. The aircraft is located on the east side of the airport, and I was given the following clearance 'taxi to runway 19L via taxiway M.' thinking, since he had both frequencys, I taxied across runway 19L on the south side. After a while, the controller asked where I was, and I told him on taxiway east. He sounded a little confused and then concern was in his voice as he realized my mistake. What I was not aware of was the new taxiway, taxiway M, was now operational. I took the route, which was the established track prior to taxiway M being opened. I was obviously in the wrong, because I assumed the old track versus recognizing the opening of the new taxiway, taxiway M.

Original NASA ASRS Text

Title: RWY INCURSION BY A C172 CFI PLT WHEN HE DOES NOT ASSOCIATE TAXI CLRNC WITH NEW TXWY AT ICT, KS.

Narrative: MY HOME BASE ARPT HAS 3 RWYS WITH 2 PARALLEL RWYS, RWY 1R-19L AND RWY 1L-19R. FOR ABOUT 6 MONTHS, THE E RWY, RWY 1R-19L, HAS BEEN OPENED AND CLOSED TO ALLOW A NEW TXWY TO BE CONSTRUCTED ON THE E SIDE OF THIS RWY. THE INCIDENT HAPPENED ON A SUNDAY MORNING, SO TFC WAS RATHER LIGHT AND THE GND AND TWR POS WERE COMBINED ON THE TWR FREQ. THE ACFT IS LOCATED ON THE E SIDE OF THE ARPT, AND I WAS GIVEN THE FOLLOWING CLRNC 'TAXI TO RWY 19L VIA TXWY M.' THINKING, SINCE HE HAD BOTH FREQS, I TAXIED ACROSS RWY 19L ON THE S SIDE. AFTER A WHILE, THE CTLR ASKED WHERE I WAS, AND I TOLD HIM ON TXWY E. HE SOUNDED A LITTLE CONFUSED AND THEN CONCERN WAS IN HIS VOICE AS HE REALIZED MY MISTAKE. WHAT I WAS NOT AWARE OF WAS THE NEW TXWY, TXWY M, WAS NOW OPERATIONAL. I TOOK THE RTE, WHICH WAS THE ESTABLISHED TRACK PRIOR TO TXWY M BEING OPENED. I WAS OBVIOUSLY IN THE WRONG, BECAUSE I ASSUMED THE OLD TRACK VERSUS RECOGNIZING THE OPENING OF THE NEW TXWY, TXWY M.

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.

Runway incursion by a C172 CFI pilot when he does not associate taxi clearance with new taxiway at ict, ks.