An EMB120 passenger flight attempts to hold short of runway 30 when hearing an atx cargo flight anno...

Attributes
ACN	495726
Time
Date	200012
Day	Fri
Local Time Of Day	1201 To 1800
Place
Locale Reference	airport : vis.airport
State Reference	CA
Altitude	agl single value : 0
Environment
Flight Conditions	VMC
Light	Night
Aircraft 1
Operator	common carrier : air carrier
Make Model Name	Brasilia EMB-120 All Series
Operating Under FAR Part	Part 119
Flight Phase	ground : holding ground : taxi
Flight Plan	IFR
Aircraft 2
Operator	common carrier : air taxi
Make Model Name	Small Transport, Low Wing, 2 Recip Eng
Operating Under FAR Part	Part 135
Flight Phase	climbout : takeoff ground : takeoff roll ground : taxi ground : position and hold
Route In Use	departure : vfr
Flight Plan	VFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Experience	flight time last 90 days : 120 flight time total : 11000 flight time type : 5000
ASRS Report	495726
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : multi engine pilot : commercial pilot : instrument
Events
Anomaly	incursion : runway non adherence : far non adherence : required legal separation other anomaly other
Independent Detector	other flight crewa
Resolutory Action	flight crew : took precautionary avoidance action
Consequence	Other
Miss Distance	horizontal : 1000 vertical : 300
Supplementary
Problem Areas	Airport Flight Crew Human Performance
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

Our aircraft loaded passenger at the terminal, listened to local AWOS and, based on wind of 310 degrees at 5 KTS, taxied to runway 30. We announced our intentions over the CTAF. Holding short of runway 30, we went off frequency for 1-2 mins to obtain our IFR release from fat approach control, and then we returned to the CTAF. The runway appeared to be clear, and we announced our intention to depart runway 30. As I began to taxi toward the hold short line, a cargo pilot announced that he was departing runway 12, so I stopped my aircraft immediately. Although we remained well clear of runway 30/12 per southeast, my aircraft's nose came to a stop about 5-6 ft past the hold short line, and I had nowhere to go to reverse that position. This all took place within a few seconds and when my first officer and I then looked down the runway a second time we saw the cargo plane in the early stages of a takeoff roll. As this was happening, I then asked the cargo pilot if he had made an earlier call on the CTAF, and he said that he had. I then told him over the TA that we were unable to completely hold short of the hold short line, and he responded by saying that he was already rotating, making what appeared to be a normal takeoff. After the cargo plane was clear of the area, we announced our departure and departed runway 30. If the cargo pilot made an earlier call that he intended to depart runway 12, it may be possible that we missed it as a result of talking to the approach controller while obtaining our IFR release. Also, why we did not notice another aircraft entering the opposite runway to ours, I do not know. The runway did appear clear, but he may have entered it quickly as we taxied toward the hold short line for runway 30. We do not know. Finally, although there is no rule about taking off downwind at uncontrolled airports, it always increases the chance of a conflict.

Original NASA ASRS Text

Title: AN EMB120 PAX FLT ATTEMPTS TO HOLD SHORT OF RWY 30 WHEN HEARING AN ATX CARGO FLT ANNOUNCE HIS DEP FROM RWY 12 AT VIS, CA.

Narrative: OUR ACFT LOADED PAX AT THE TERMINAL, LISTENED TO LCL AWOS AND, BASED ON WIND OF 310 DEGS AT 5 KTS, TAXIED TO RWY 30. WE ANNOUNCED OUR INTENTIONS OVER THE CTAF. HOLDING SHORT OF RWY 30, WE WENT OFF FREQ FOR 1-2 MINS TO OBTAIN OUR IFR RELEASE FROM FAT APCH CTL, AND THEN WE RETURNED TO THE CTAF. THE RWY APPEARED TO BE CLR, AND WE ANNOUNCED OUR INTENTION TO DEPART RWY 30. AS I BEGAN TO TAXI TOWARD THE HOLD SHORT LINE, A CARGO PLT ANNOUNCED THAT HE WAS DEPARTING RWY 12, SO I STOPPED MY ACFT IMMEDIATELY. ALTHOUGH WE REMAINED WELL CLR OF RWY 30/12 PER SE, MY ACFT'S NOSE CAME TO A STOP ABOUT 5-6 FT PAST THE HOLD SHORT LINE, AND I HAD NOWHERE TO GO TO REVERSE THAT POS. THIS ALL TOOK PLACE WITHIN A FEW SECONDS AND WHEN MY FO AND I THEN LOOKED DOWN THE RWY A SECOND TIME WE SAW THE CARGO PLANE IN THE EARLY STAGES OF A TKOF ROLL. AS THIS WAS HAPPENING, I THEN ASKED THE CARGO PLT IF HE HAD MADE AN EARLIER CALL ON THE CTAF, AND HE SAID THAT HE HAD. I THEN TOLD HIM OVER THE TA THAT WE WERE UNABLE TO COMPLETELY HOLD SHORT OF THE HOLD SHORT LINE, AND HE RESPONDED BY SAYING THAT HE WAS ALREADY ROTATING, MAKING WHAT APPEARED TO BE A NORMAL TKOF. AFTER THE CARGO PLANE WAS CLR OF THE AREA, WE ANNOUNCED OUR DEP AND DEPARTED RWY 30. IF THE CARGO PLT MADE AN EARLIER CALL THAT HE INTENDED TO DEPART RWY 12, IT MAY BE POSSIBLE THAT WE MISSED IT AS A RESULT OF TALKING TO THE APCH CTLR WHILE OBTAINING OUR IFR RELEASE. ALSO, WHY WE DID NOT NOTICE ANOTHER ACFT ENTERING THE OPPOSITE RWY TO OURS, I DO NOT KNOW. THE RWY DID APPEAR CLR, BUT HE MAY HAVE ENTERED IT QUICKLY AS WE TAXIED TOWARD THE HOLD SHORT LINE FOR RWY 30. WE DO NOT KNOW. FINALLY, ALTHOUGH THERE IS NO RULE ABOUT TAKING OFF DOWNWIND AT UNCTLED ARPTS, IT ALWAYS INCREASES THE CHANCE OF A CONFLICT.

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.

An EMB120 passenger flight attempts to hold short of runway 30 when hearing an atx cargo flight announce his departure from runway 12 at visibility, ca.