Pilot fails to adhere to controller's instructions at fwa for an intersection departure; crossing an active runway resulting in a go around.

Home

Browse by month

Random

Latest

About

Contact

Attributes
ACN	649686
Time
Date	200503
Local Time Of Day	0601 To 1200
Place
Locale Reference	airport : fwa.airport
State Reference	IN
Altitude	agl single value : 0
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tower : fwa.tower
Operator	common carrier : charter
Make Model Name	Small Aircraft Low Wing 2 Eng Retractable Gear
Operating Under FAR Part	Part 91
Flight Phase	ground : taxi
Flight Plan	IFR
Aircraft 2
Controlling Facilities	tower : fwa.tower
Make Model Name	Any Unknown or Unlisted Aircraft Manufacturer
Flight Phase	descent : approach
Person 1
Affiliation	company : charter
Function	flight crew : single pilot
Qualification	pilot : instrument pilot : multi engine
Experience	flight time last 90 days : 50 flight time total : 2500 flight time type : 75
ASRS Report	649686
Person 2
Affiliation	government : faa
Function	controller : ground
Events
Anomaly	conflict : ground less severe incursion : runway non adherence : published procedure non adherence : far non adherence : clearance
Independent Detector	other flight crewa
Resolutory Action	controller : issued new clearance flight crew : executed go around
Consequence	faa : reviewed incident with flight crew
Miss Distance	horizontal : 7000 vertical : 500
Supplementary
Problem Areas	Flight Crew Human Performance
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

I was cleared 'taxi to runway 32 at charlie intersection.' I read back 'taxi runway 32 via charlie intersection.' I believed I was cleared to the departure end of runway 32 when in fact the ground controller wanted me to taxi to taxiway C and runway 32 and make an intersection departure. I proceeded across (unknowingly an active runway 23) a runway to get to the departure end of runway 32. No hold short clearance was issued. As I proceeded across runway 23; I noticed a cpr jet on final for runway 23. The jet made a go around and I received a couple of radio calls stating I taxied where I should not have. I was informed to contact fwa tower via phone after my departure. The only thing that struck me was that I should have asked for clarified instructions -- I didn't realize controllers suggested midfield departures. I do know I can request intersection departures; but I didn't know controllers can request them of me. Once cleared to runway 32 with no hold shorts or stop short of active runways; I thought I had unrestr taxi to runway 32.

Original NASA ASRS Text

Title: PLT FAILS TO ADHERE TO CTLR'S INSTRUCTIONS AT FWA FOR AN INTXN DEP; XING AN ACTIVE RWY RESULTING IN A GAR.

Narrative: I WAS CLRED 'TAXI TO RWY 32 AT CHARLIE INTXN.' I READ BACK 'TAXI RWY 32 VIA CHARLIE INTXN.' I BELIEVED I WAS CLRED TO THE DEP END OF RWY 32 WHEN IN FACT THE GND CTLR WANTED ME TO TAXI TO TXWY C AND RWY 32 AND MAKE AN INTXN DEP. I PROCEEDED ACROSS (UNKNOWINGLY AN ACTIVE RWY 23) A RWY TO GET TO THE DEP END OF RWY 32. NO HOLD SHORT CLRNC WAS ISSUED. AS I PROCEEDED ACROSS RWY 23; I NOTICED A CPR JET ON FINAL FOR RWY 23. THE JET MADE A GAR AND I RECEIVED A COUPLE OF RADIO CALLS STATING I TAXIED WHERE I SHOULD NOT HAVE. I WAS INFORMED TO CONTACT FWA TWR VIA PHONE AFTER MY DEP. THE ONLY THING THAT STRUCK ME WAS THAT I SHOULD HAVE ASKED FOR CLARIFIED INSTRUCTIONS -- I DIDN'T REALIZE CTLRS SUGGESTED MIDFIELD DEPS. I DO KNOW I CAN REQUEST INTXN DEPS; BUT I DIDN'T KNOW CTLRS CAN REQUEST THEM OF ME. ONCE CLRED TO RWY 32 WITH NO HOLD SHORTS OR STOP SHORT OF ACTIVE RWYS; I THOUGHT I HAD UNRESTR TAXI TO RWY 32.

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.