P80 controller issues traffic alert to departing FK28 on BE55 entering the wrong traffic pattern. Controller concerned with air carrier-GA mix at pdx.

Home

Browse by month

Random

Latest

About

Contact

Attributes
ACN	510489
Time
Date	200105
Day	Mon
Place
Locale Reference	airport : pdx.airport
State Reference	OR
Altitude	msl single value : 1000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tower : pdx.tower
Operator	common carrier : air carrier
Make Model Name	F28 Undifferentiated or Other Model
Operating Under FAR Part	Part 121
Flight Phase	climbout : initial climbout : takeoff
Flight Plan	IFR
Aircraft 2
Controlling Facilities	tower : pdx.tower
Operator	general aviation : personal
Make Model Name	Baron 55/Cochise
Operating Under FAR Part	Part 91
Navigation In Use	other
Flight Phase	descent : approach
Route In Use	approach : traffic pattern
Flight Plan	VFR
Person 1
Affiliation	government : faa
Function	controller : local
Qualification	controller : radar
Experience	controller limited radar : 10 controller military : 4 controller non radar : 1 controller supervisory : 1
ASRS Report	510489
Person 2
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Events
Anomaly	conflict : airborne critical non adherence : clearance non adherence : required legal separation other spatial deviation
Independent Detector	atc equipment : conflict alert other controllera
Resolutory Action	controller : issued alert controller : issued new clearance controller : separated traffic
Miss Distance	horizontal : 1500 vertical : 200
Supplementary
Problem Areas	Airport Flight Crew Human Performance
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

FK28 departing runway 28L. BE55 inbound from north for runway 28R. BE55 was on local 1 frequency, FK28 on my frequency (local 2). I noticed that the BE55 was not entering the pattern as he should and brought this to local 1's attention. The FK28 had just become airborne and I issued a traffic alert on the BE55 who was continuing sbound. The FK28 reported the BE55 in sight and did not appear to take any evasive action. The BE55 pilot later stated that he was not aware that there were parallel runways at pdx. (Even though he acknowledged runway 28R as his assigned runway.) the local 1 controller had numerous VFR aircraft on his frequency that were all requiring extra attention. Air carrier and GA traffic don't mix. What has to happen before something is done to segregate this traffic?

Original NASA ASRS Text

Title: P80 CTLR ISSUES TFC ALERT TO DEPARTING FK28 ON BE55 ENTERING THE WRONG TFC PATTERN. CTLR CONCERNED WITH ACR-GA MIX AT PDX.

Narrative: FK28 DEPARTING RWY 28L. BE55 INBOUND FROM N FOR RWY 28R. BE55 WAS ON LOCAL 1 FREQ, FK28 ON MY FREQ (LOCAL 2). I NOTICED THAT THE BE55 WAS NOT ENTERING THE PATTERN AS HE SHOULD AND BROUGHT THIS TO LOCAL 1'S ATTN. THE FK28 HAD JUST BECOME AIRBORNE AND I ISSUED A TFC ALERT ON THE BE55 WHO WAS CONTINUING SBOUND. THE FK28 RPTED THE BE55 IN SIGHT AND DID NOT APPEAR TO TAKE ANY EVASIVE ACTION. THE BE55 PLT LATER STATED THAT HE WAS NOT AWARE THAT THERE WERE PARALLEL RWYS AT PDX. (EVEN THOUGH HE ACKNOWLEDGED RWY 28R AS HIS ASSIGNED RWY.) THE LOCAL 1 CTLR HAD NUMEROUS VFR ACFT ON HIS FREQ THAT WERE ALL REQUIRING EXTRA ATTN. ACR AND GA TFC DON'T MIX. WHAT HAS TO HAPPEN BEFORE SOMETHING IS DONE TO SEGREGATE THIS TFC?

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.