Aircraft landed on an intersecting runway simultaneously with an air carrier, resulting in a high ap...

Attributes
ACN	113229
Time
Date	198906
Day	Thu
Local Time Of Day	1801 To 2400
Place
Locale Reference	airport : roc
State Reference	NY
Altitude	agl bound lower : 0 agl bound upper : 1000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tower : roc
Operator	general aviation : instructional
Make Model Name	Any Unknown or Unlisted Aircraft Manufacturer
Flight Phase	landing other
Flight Plan	None
Aircraft 2
Operator	common carrier : air carrier
Make Model Name	Medium Large Transport, Low Wing, 2 Turbojet Eng
Flight Phase	climbout : takeoff climbout : intermediate altitude
Route In Use	departure other
Flight Plan	IFR
Person 1
Affiliation	Other
Function	flight crew : single pilot
Qualification	controller : developmental pilot : instrument pilot : private
Experience	flight time last 90 days : 30 flight time total : 400 flight time type : 150
ASRS Report	113229
Person 2
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Events
Anomaly	other anomaly other
Independent Detector	other flight crewa
Resolutory Action	flight crew : took evasive action
Consequence	Other
Miss Distance	horizontal : 4000 vertical : 100
Supplementary
Primary Problem	ATC Human Performance
Air Traffic Incident	other

Narrative:

Radar handed me over to roc tower for runway 10 approximately 4 mi final. Local controller placed air carrier X in position runway 4 (intersecting runways). Local control cleared me to land runway 10. Approximately 1.5 mi out on final, air carrier X was cleared for takeoff causing a crossing path plus potential for wake turbulence, no warning issued. I questioned the tower in case he forgot I was on final to runway 10. Again I was cleared to land runway 10. Meanwhile air carrier Y was cleared to land on runway 4. I was forced to make a much higher than normal approach to runway 10 to avoid the intersection. Had I landed on runway 10 as cleared, air carrier Y and my aircraft would have come within approximately 1000' to 500' as I passed the intersection. Local controller did not issue a restriction to hold short of the intersection to air carrier Y, nor did he issue traffic advisory. It appears the local controller committed himself to a bad plan. Roc in general has been using 'visual separation' to cross jet traffic over small aircraft posing a threat of wake turbulence accidents.

Original NASA ASRS Text

Title: ACFT LANDED ON AN INTERSECTING RWY SIMULTANEOUSLY WITH AN ACR, RESULTING IN A HIGH APCH.

Narrative: RADAR HANDED ME OVER TO ROC TWR FOR RWY 10 APPROX 4 MI FINAL. LCL CTLR PLACED ACR X IN POSITION RWY 4 (INTERSECTING RWYS). LCL CTL CLRED ME TO LAND RWY 10. APPROX 1.5 MI OUT ON FINAL, ACR X WAS CLRED FOR TKOF CAUSING A XING PATH PLUS POTENTIAL FOR WAKE TURBULENCE, NO WARNING ISSUED. I QUESTIONED THE TWR IN CASE HE FORGOT I WAS ON FINAL TO RWY 10. AGAIN I WAS CLRED TO LAND RWY 10. MEANWHILE ACR Y WAS CLRED TO LAND ON RWY 4. I WAS FORCED TO MAKE A MUCH HIGHER THAN NORMAL APCH TO RWY 10 TO AVOID THE INTXN. HAD I LANDED ON RWY 10 AS CLRED, ACR Y AND MY ACFT WOULD HAVE COME WITHIN APPROX 1000' TO 500' AS I PASSED THE INTXN. LCL CTLR DID NOT ISSUE A RESTRICTION TO HOLD SHORT OF THE INTXN TO ACR Y, NOR DID HE ISSUE TFC ADVISORY. IT APPEARS THE LCL CTLR COMMITTED HIMSELF TO A BAD PLAN. ROC IN GENERAL HAS BEEN USING 'VISUAL SEPARATION' TO CROSS JET TFC OVER SMALL ACFT POSING A THREAT OF WAKE TURBULENCE ACCIDENTS.

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.

Aircraft landed on an intersecting runway simultaneously with an air carrier, resulting in a high approach.