Ground conflict between light transport X taxiing onto runway and small aircraft Y on final at 49J.

Attributes
ACN	143972
Time
Date	199004
Day	Sun
Local Time Of Day	1201 To 1800
Place
Locale Reference	airport : 49j
State Reference	SC
Altitude	agl bound lower : 0 agl bound upper : 200
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Operator	common carrier : air carrier
Make Model Name	Light Transport, Low Wing, 2 Turboprop Eng
Flight Phase	ground other : taxi
Flight Plan	IFR
Aircraft 2
Make Model Name	Small Aircraft, High Wing, 1 Eng, Fixed Gear
Flight Phase	descent : approach landing : go around other
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : cfi pilot : atp
Experience	flight time last 90 days : 125 flight time total : 4100 flight time type : 65
ASRS Report	143972
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : commercial pilot : instrument
Events
Anomaly	conflict : ground less severe incursion : runway non adherence : published procedure other spatial deviation
Independent Detector	other flight crewa
Resolutory Action	other
Consequence	Other
Supplementary
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

We were taxiing onto the runway (R21) at hilton head airport when my first officer said there is an small aircraft Y turning final. The aircraft on final initiated a go around when he noticed that we were taxiing onto the runway. There was nothing we could do to evade the aircraft if he had landed since it was not possible to maneuver light transport X off the runway in time. I did not hear a radio call by small aircraft Y before or while taxiing onto the runway, or while taxiing out. However we did not initiate a call, either. There are several contributing factors. One is a fatigue factor of a 15 hour duty day the day before. The other is the first officer announcement to passenger while taxiing. The first officer was still making an passenger announcement while I was calling departure control for clearance. I believe a prerecorded passenger announcement on aircraft west/O a F/a would be of great benefit at airports where there is a short taxi time. This is, however, also a case of not enough diligence on our part and or not making the announcement of our intentions.

Original NASA ASRS Text

Title: GND CONFLICT BETWEEN LTT X TAXIING ONTO RWY AND SMA Y ON FINAL AT 49J.

Narrative: WE WERE TAXIING ONTO THE RWY (R21) AT HILTON HEAD ARPT WHEN MY F/O SAID THERE IS AN SMA Y TURNING FINAL. THE ACFT ON FINAL INITIATED A GAR WHEN HE NOTICED THAT WE WERE TAXIING ONTO THE RWY. THERE WAS NOTHING WE COULD DO TO EVADE THE ACFT IF HE HAD LANDED SINCE IT WAS NOT POSSIBLE TO MANEUVER LTT X OFF THE RWY IN TIME. I DID NOT HEAR A RADIO CALL BY SMA Y BEFORE OR WHILE TAXIING ONTO THE RWY, OR WHILE TAXIING OUT. HOWEVER WE DID NOT INITIATE A CALL, EITHER. THERE ARE SEVERAL CONTRIBUTING FACTORS. ONE IS A FATIGUE FACTOR OF A 15 HR DUTY DAY THE DAY BEFORE. THE OTHER IS THE F/O ANNOUNCEMENT TO PAX WHILE TAXIING. THE F/O WAS STILL MAKING AN PAX ANNOUNCEMENT WHILE I WAS CALLING DEP CTL FOR CLRNC. I BELIEVE A PRERECORDED PAX ANNOUNCEMENT ON ACFT W/O A F/A WOULD BE OF GREAT BENEFIT AT ARPTS WHERE THERE IS A SHORT TAXI TIME. THIS IS, HOWEVER, ALSO A CASE OF NOT ENOUGH DILIGENCE ON OUR PART AND OR NOT MAKING THE ANNOUNCEMENT OF OUR INTENTIONS.

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.