Uncoord unauthorized runway entry by air carrier mdt at non tower airport FSS.

Attributes
ACN	228072
Time
Date	199212
Day	Fri
Local Time Of Day	0601 To 1200
Place
Locale Reference	airport : ewn
State Reference	NC
Altitude	agl bound lower : 0 agl bound upper : 0
Environment
Flight Conditions	VMC
Light	Dawn
Aircraft 1
Controlling Facilities	tower : slc
Operator	common carrier : air carrier
Make Model Name	Medium Transport, High Wing, 2 Turboprop Eng
Flight Phase	ground : holding ground other : taxi
Flight Plan	IFR
Aircraft 2
Operator	general aviation : personal
Make Model Name	Small Transport, Low Wing, 2 Recip Eng
Flight Phase	descent : approach landing other
Route In Use	approach : straight in
Flight Plan	VFR
Person 1
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : atp
Experience	flight time last 90 days : 230 flight time total : 3500 flight time type : 580
ASRS Report	228072
Person 2
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Events
Anomaly	incursion : runway non adherence : published procedure non adherence : far other anomaly other
Independent Detector	other flight crewa
Resolutory Action	flight crew : exited adverse environment
Consequence	Other
Miss Distance	horizontal : 12000 vertical : 700
Supplementary
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

Taxiing out for departure at ewn, we announced that we were 'taxiing to runway 22.' ewn FSS released our flight, and we announced that we were 'departing runway 22.' as we taxied onto the runway, a twin small transport announced he was on short final to runway 4. We taxied straight ahead and cleared the runway in ample time, but here are some of the problems I saw. FSS did not give TA of known inbound traffic. Approaching aircraft was not announcing position or intentions. (We were monitoring frequency for approximately 15 mins while being deiced prior to departure). Captain did not adequately visually clear his side of aircraft. My only recommendation is that everyone involved follow the uncontrolled procedures a little closer, ie, FSS announcing inbound and outbound traffic. Aircraft in airport vicinity make clear and timely announcements. Both crew members check both directions visually. This situation was not that critical, but had the potential to be, another item I will personally do is to turn TCASII on while taxiing at uncontrolled fields. Any additional information can't hurt.

Original NASA ASRS Text

Title: UNCOORD UNAUTHORIZED RWY ENTRY BY ACR MDT AT NON TWR ARPT FSS.

Narrative: TAXIING OUT FOR DEP AT EWN, WE ANNOUNCED THAT WE WERE 'TAXIING TO RWY 22.' EWN FSS RELEASED OUR FLT, AND WE ANNOUNCED THAT WE WERE 'DEPARTING RWY 22.' AS WE TAXIED ONTO THE RWY, A TWIN SMT ANNOUNCED HE WAS ON SHORT FINAL TO RWY 4. WE TAXIED STRAIGHT AHEAD AND CLRED THE RWY IN AMPLE TIME, BUT HERE ARE SOME OF THE PROBLEMS I SAW. FSS DID NOT GIVE TA OF KNOWN INBOUND TFC. APCHING ACFT WAS NOT ANNOUNCING POS OR INTENTIONS. (WE WERE MONITORING FREQ FOR APPROX 15 MINS WHILE BEING DEICED PRIOR TO DEP). CAPT DID NOT ADEQUATELY VISUALLY CLR HIS SIDE OF ACFT. MY ONLY RECOMMENDATION IS THAT EVERYONE INVOLVED FOLLOW THE UNCTLED PROCS A LITTLE CLOSER, IE, FSS ANNOUNCING INBOUND AND OUTBOUND TFC. ACFT IN ARPT VICINITY MAKE CLR AND TIMELY ANNOUNCEMENTS. BOTH CREW MEMBERS CHK BOTH DIRECTIONS VISUALLY. THIS SITUATION WAS NOT THAT CRITICAL, BUT HAD THE POTENTIAL TO BE, ANOTHER ITEM I WILL PERSONALLY DO IS TO TURN TCASII ON WHILE TAXIING AT UNCTLED FIELDS. ANY ADDITIONAL INFO CAN'T HURT.

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.