Charter small transport unauthorized runway crossing causes takeoff abort.

Attributes
ACN	82166
Time
Date	198802
Day	Wed
Local Time Of Day	1201 To 1800
Place
Locale Reference	airport : sby
State Reference	MD
Altitude	agl bound lower : 0 agl bound upper : 0
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Operator	general aviation : instructional
Make Model Name	Small Transport, Low Wing, 2 Turboprop Eng
Flight Phase	ground : holding ground other : taxi
Flight Plan	IFR
Aircraft 2
Make Model Name	Small Transport, Low Wing, 2 Turboprop Eng
Flight Phase	climbout : takeoff other
Person 1
Affiliation	Other
Function	flight crew : first officer oversight : pic
Qualification	pilot : cfi pilot : atp
Experience	flight time last 90 days : 950 flight time total : 10400 flight time type : 50
ASRS Report	82166
Person 2
Function	flight crew : captain
Qualification	pilot : commercial pilot : instrument
Events
Anomaly	conflict : ground critical incursion : runway
Independent Detector	other flight crewa
Resolutory Action	none taken : detected after the fact
Consequence	Other
Miss Distance	horizontal : 300 vertical : 0
Supplementary
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

Salisbury airport is a non tower airport. Advisory information is handled through the FSS located on the field. However, IFR clrncs are obtained through patuxent river approach which is remoted on the field. After engine start we obtained runway in use information from sby FSS and were advised to obtain our IFR clearance from patuxent on a different frequency. Our taxi route required our crossing the runway in use and during this time we were obtaining our IFR clearance on a frequency different from the advisory frequency. Nearing the point we would cross the runway in use the sic (flying as PIC) asked 'how does it look on that side?' I scanned the sky on the approach to the runway in use and reported it as all clear. Looking to the same area as we crossed the runway I noticed an small transport aborting his takeoff about 100 yards from us. The pilot must have been furious at us. After switching back to the FSS frequency they had some strong advice for us. We certainly deserved it. Our wheels should never have moved while we were off the advisory frequency. We would certainly have heard the pilot of the small transport advising traffic of his departure.

Original NASA ASRS Text

Title: CHARTER SMT UNAUTH RWY CROSSING CAUSES TKOF ABORT.

Narrative: SALISBURY ARPT IS A NON TWR ARPT. ADVISORY INFO IS HANDLED THROUGH THE FSS LOCATED ON THE FIELD. HOWEVER, IFR CLRNCS ARE OBTAINED THROUGH PATUXENT RIVER APCH WHICH IS REMOTED ON THE FIELD. AFTER ENG START WE OBTAINED RWY IN USE INFO FROM SBY FSS AND WERE ADVISED TO OBTAIN OUR IFR CLRNC FROM PATUXENT ON A DIFFERENT FREQ. OUR TAXI RTE REQUIRED OUR XING THE RWY IN USE AND DURING THIS TIME WE WERE OBTAINING OUR IFR CLRNC ON A FREQ DIFFERENT FROM THE ADVISORY FREQ. NEARING THE POINT WE WOULD CROSS THE RWY IN USE THE SIC (FLYING AS PIC) ASKED 'HOW DOES IT LOOK ON THAT SIDE?' I SCANNED THE SKY ON THE APCH TO THE RWY IN USE AND RPTED IT AS ALL CLR. LOOKING TO THE SAME AREA AS WE CROSSED THE RWY I NOTICED AN SMT ABORTING HIS TKOF ABOUT 100 YARDS FROM US. THE PLT MUST HAVE BEEN FURIOUS AT US. AFTER SWITCHING BACK TO THE FSS FREQ THEY HAD SOME STRONG ADVICE FOR US. WE CERTAINLY DESERVED IT. OUR WHEELS SHOULD NEVER HAVE MOVED WHILE WE WERE OFF THE ADVISORY FREQ. WE WOULD CERTAINLY HAVE HEARD THE PLT OF THE SMT ADVISING TFC OF HIS DEP.

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