Landing on occupied runway.

Attributes
ACN	159668
Time
Date	199010
Day	Sat
Local Time Of Day	0601 To 1200
Place
Locale Reference	airport : syv
State Reference	GA
Altitude	agl bound lower : 0 agl bound upper : 0
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Operator	general aviation : personal
Make Model Name	Small Transport, Low Wing, 2 Recip Eng
Flight Phase	descent : approach landing other
Flight Plan	None
Aircraft 2
Make Model Name	Small Transport, Low Wing, 2 Recip Eng
Flight Phase	ground : holding ground other : taxi landing other
Flight Plan	None
Person 1
Affiliation	Other
Function	flight crew : single pilot
Qualification	pilot : commercial pilot : instrument
Experience	flight time last 90 days : 50 flight time total : 3000 flight time type : 160
ASRS Report	159668
Person 2
Affiliation	Other
Function	flight crew : single pilot
Events
Anomaly	conflict : ground less severe incursion : runway non adherence : published procedure other spatial deviation
Independent Detector	other flight crewa
Resolutory Action	none taken : anomaly accepted
Consequence	Other
Supplementary
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

2 twin engine aircraft were in the traffic pattern at the same time. While making a visibility approach to the airport for landing on runway 19, I saw the other aircraft turning from base to final for the same runway. I announced that I would follow the other aircraft to the runway, and slowed to do so. There was never any problem with in-flight sep of the 2 aircraft. After the other aircraft landed, I saw it turn to the left, which I thought was going to be a turn off of the runway. When the other pilot reached a position in his turn where he could see me, he stopped on the runway instead of clearing. Because my aircraft was in landing confign and at slow airspeed, and because there was no question that I had more than enough available runway, I decided that landing was the prudent choice rather than attempting to abort the landing. No evasive action was necessary on the part of either pilot and no collision hazard existed. While the outcome of this incident was never in doubt, I feel that anytime you have 2 aircraft inadvertently present on the same runway at the same time, there exists a potentially dangerous situation. I believe that this incident could have been avoided by better communications between the aircraft, proper traffic pattern procedures, and more expeditious runway clearing.

Original NASA ASRS Text

Title: LNDG ON OCCUPIED RWY.

Narrative: 2 TWIN ENG ACFT WERE IN THE TFC PATTERN AT THE SAME TIME. WHILE MAKING A VIS APCH TO THE ARPT FOR LNDG ON RWY 19, I SAW THE OTHER ACFT TURNING FROM BASE TO FINAL FOR THE SAME RWY. I ANNOUNCED THAT I WOULD FOLLOW THE OTHER ACFT TO THE RWY, AND SLOWED TO DO SO. THERE WAS NEVER ANY PROB WITH INFLT SEP OF THE 2 ACFT. AFTER THE OTHER ACFT LANDED, I SAW IT TURN TO THE LEFT, WHICH I THOUGHT WAS GOING TO BE A TURN OFF OF THE RWY. WHEN THE OTHER PLT REACHED A POS IN HIS TURN WHERE HE COULD SEE ME, HE STOPPED ON THE RWY INSTEAD OF CLRING. BECAUSE MY ACFT WAS IN LNDG CONFIGN AND AT SLOW AIRSPD, AND BECAUSE THERE WAS NO QUESTION THAT I HAD MORE THAN ENOUGH AVAILABLE RWY, I DECIDED THAT LNDG WAS THE PRUDENT CHOICE RATHER THAN ATTEMPTING TO ABORT THE LNDG. NO EVASIVE ACTION WAS NECESSARY ON THE PART OF EITHER PLT AND NO COLLISION HAZARD EXISTED. WHILE THE OUTCOME OF THIS INCIDENT WAS NEVER IN DOUBT, I FEEL THAT ANYTIME YOU HAVE 2 ACFT INADVERTENTLY PRESENT ON THE SAME RWY AT THE SAME TIME, THERE EXISTS A POTENTIALLY DANGEROUS SITUATION. I BELIEVE THAT THIS INCIDENT COULD HAVE BEEN AVOIDED BY BETTER COMS BTWN THE ACFT, PROPER TFC PATTERN PROCS, AND MORE EXPEDITIOUS RWY CLRING.

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.