Small aircraft X runway incursion had less than standard separation from cpr Y landing. System error...

Attributes
ACN	265876
Time
Date	199403
Day	Sat
Local Time Of Day	1201 To 1800
Place
Locale Reference	atc facility : ptk
State Reference	MI
Altitude	agl bound lower : 0 agl bound upper : 20
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tower : ptk
Operator	general aviation : personal
Make Model Name	Any Unknown or Unlisted Aircraft Manufacturer
Operating Under FAR Part	Part 91
Flight Phase	ground other : taxi
Flight Plan	None
Aircraft 2
Operator	general aviation : corporate
Make Model Name	Any Unknown or Unlisted Aircraft Manufacturer
Operating Under FAR Part	Part 91
Flight Phase	descent : approach landing other
Person 1
Affiliation	Other
Function	flight crew : single pilot
Qualification	pilot : atp
Experience	flight time last 90 days : 30 flight time total : 3235 flight time type : 25
ASRS Report	265876
Person 2
Affiliation	Other
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Events
Anomaly	conflict : nmac conflict : ground critical incursion : runway non adherence : published procedure non adherence : required legal separation
Independent Detector	other controllera other flight crewa
Resolutory Action	controller : issued new clearance other other
Consequence	Other
Miss Distance	vertical : 20
Supplementary
Primary Problem	ATC Human Performance
Air Traffic Incident	Intra Facility Coordination Failure Operational Error

Narrative:

Small aircraft X, a clearance was received to taxi to the north t-hangars via runway 36 and taxiway east. After turning north and commencing taxi on runway 36, a high wing cessna was observed overshooting final on right base to runway 27R. Its flight path looked as though it might cross that of an airplane approaching straight in for runway 27L. The straight in arrival turned out to be a fast moving cpr Y jet. It was low and rapidly approaching our position on runway 36. I advanced the throttle to get out of its path, but too late. The 125 executed a missed approach, but with spool up time etc, it continued descending narrowly missing our airplane. Ground control said nothing after giving us the initial taxi clearance. Based on this event, I recommend that ground control routinely hold aircraft taxiing on runway 36 short of the approach path to runway 27L when there are close in arrs, especially jets, for runway 27L. Due to simultaneous operations on the closely spaced parallel runways, there can be distrs for pilots and controllers alike.

Original NASA ASRS Text

Title: SMA X RWY INCURSION HAD LTSS FROM CPR Y LNDG. SYS ERROR.

Narrative: SMA X, A CLRNC WAS RECEIVED TO TAXI TO THE N T-HANGARS VIA RWY 36 AND TXWY E. AFTER TURNING N AND COMMENCING TAXI ON RWY 36, A HIGH WING CESSNA WAS OBSERVED OVERSHOOTING FINAL ON R BASE TO RWY 27R. ITS FLT PATH LOOKED AS THOUGH IT MIGHT CROSS THAT OF AN AIRPLANE APCHING STRAIGHT IN FOR RWY 27L. THE STRAIGHT IN ARR TURNED OUT TO BE A FAST MOVING CPR Y JET. IT WAS LOW AND RAPIDLY APCHING OUR POS ON RWY 36. I ADVANCED THE THROTTLE TO GET OUT OF ITS PATH, BUT TOO LATE. THE 125 EXECUTED A MISSED APCH, BUT WITH SPOOL UP TIME ETC, IT CONTINUED DSNDING NARROWLY MISSING OUR AIRPLANE. GND CTL SAID NOTHING AFTER GIVING US THE INITIAL TAXI CLRNC. BASED ON THIS EVENT, I RECOMMEND THAT GND CTL ROUTINELY HOLD ACFT TAXIING ON RWY 36 SHORT OF THE APCH PATH TO RWY 27L WHEN THERE ARE CLOSE IN ARRS, ESPECIALLY JETS, FOR RWY 27L. DUE TO SIMULTANEOUS OPS ON THE CLOSELY SPACED PARALLEL RWYS, THERE CAN BE DISTRS FOR PLTS AND CTLRS ALIKE.

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.