SR22 pilot reported another aircraft landing on an intersecting runway executed a go-around when the...

Attributes
ACN	1381859
Time
Date	201608
Local Time Of Day	1801-2400
Place
Locale Reference	PNS.Airport
State Reference	FL
Environment
Flight Conditions	VMC
Light	Night
Aircraft 1
Make Model Name	SR22
Operating Under FAR Part	Part 91
Flight Phase	Landing
Route In Use	Visual Approach Direct
Flight Plan	IFR
Aircraft 2
Make Model Name	Commercial Fixed Wing
Operating Under FAR Part	Part 121
Flight Phase	Final Approach
Route In Use	Visual Approach
Flight Plan	IFR
Person 1
Function	Single Pilot
Qualification	Flight Crew Instrument Flight Crew Private
Experience	Flight Crew Last 90 Days 76 Flight Crew Total 2809 Flight Crew Type 2460
Events
Anomaly	ATC Issue All Types Conflict Ground Conflict Less Severe

Narrative:

I was flying my aircraft and cleared for a visual approach to runway 26. I was told I was number one for landing. I continued inbound to make a normal landing. Several feet before touching down; the tower controller called and asked if I could make taxiway charlie. I was in the midst of a critical phase of flight (landing touchdown) and told them to hold on; my focus was on landing the airplane that very moment; not determining if I could make an expedited turn-off. As I touched down and went to convey that I couldn't make the taxiway they requested; ATC was already on the radio giving instructions to an airliner who they cleared to land on an intersecting runway (17) to go around.the ATIS at the time indicated runway 26 was in use; the one I was using. The winds favored 26. ATC cleared me on runway 26 and then cleared the airliner on runway 17. I believe ATC misjudged the speeds and/or the arrival time at the airport thinking that I would be on the ground and clear of the active runway before the airliner arrived to land on runway 17.the solution to prevent a recurrence is to require airplanes to land on the active runway when other aircraft are present. Additional responsiveness of ATC to recognize and react to this conflict well before it occur would also have prevented it from happening.

Original NASA ASRS Text

Title: SR22 pilot reported another aircraft landing on an intersecting runway executed a go-around when the Tower Controller misjudged the spacing.

Narrative: I was flying my aircraft and cleared for a visual approach to runway 26. I was told I was number one for landing. I continued inbound to make a normal landing. Several feet before touching down; the Tower Controller called and asked if I could make taxiway Charlie. I was in the midst of a critical phase of flight (landing touchdown) and told them to hold on; my focus was on landing the airplane that very moment; not determining if I could make an expedited turn-off. As I touched down and went to convey that I couldn't make the taxiway they requested; ATC was already on the radio giving instructions to an airliner who they cleared to land on an intersecting runway (17) to go around.The ATIS at the time indicated runway 26 was in use; the one I was using. The winds favored 26. ATC cleared me on runway 26 and then cleared the airliner on runway 17. I believe ATC misjudged the speeds and/or the arrival time at the airport thinking that I would be on the ground and clear of the active runway before the airliner arrived to land on runway 17.The solution to prevent a recurrence is to require airplanes to land on the active runway when other aircraft are present. Additional responsiveness of ATC to recognize and react to this conflict well before it occur would also have prevented it from happening.

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

SR22 pilot reported another aircraft landing on an intersecting runway executed a go-around when the tower controller misjudged the spacing.