 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
BE35 and PA34 had less than standard separation when tower local controller had both aircraft on final for the same runway.
| Attributes | |
| ACN | 416808 |
| Time | |
| Date | 199810 |
| Day | Tue |
| Local Time Of Day | 1201 To 1800 |
| Place | |
| Locale Reference | atc facility : zzz airport : zzz |
| State Reference | US |
| Altitude | agl bound lower : 600 agl bound upper : 600 |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Controlling Facilities | tower : zzz |
| Operator | general aviation : personal |
| Make Model Name | Small Aircraft, Low Wing, 1 Eng, Retractable Gear |
| Flight Phase | descent : approach |
| Flight Plan | None |
| Aircraft 2 | |
| Make Model Name | Small Aircraft, Low Wing, 2 Eng, Retractable Gear |
| Flight Phase | descent : approach |
| Person 1 | |
| Affiliation | Other |
| Function | flight crew : single pilot |
| Qualification | pilot : private pilot : instrument |
| Experience | flight time last 90 days : 24 flight time total : 1100 flight time type : 890 |
| ASRS Report | 416808 |
| Person 2 | |
| Affiliation | Other |
| Function | flight crew : single pilot |
| Qualification | pilot : private |
| Events | |
| Anomaly | conflict : airborne less severe other anomaly other |
| Independent Detector | other flight crewa |
| Resolutory Action | controller : issued new clearance flight crew : took evasive action other |
| Consequence | Other |
| Miss Distance | horizontal : 6000 vertical : 100 |
| Supplementary | |
| Primary Problem | ATC Human Performance |
| Air Traffic Incident | Operational Error |
Narrative:
Left base for runway 34, #2 with king air #1, report left downwind to left base. (King air was actually right downwind and base.) tower advised 'IFR traffic waiting takeoff on runway 34, change to left downwind for runway 30.' flew left downwind and base to runway 30. In position to turn final almost, when saw twin 1 1/4 - 2 mi on 280 degree course, apparently for runway 30 landing. We both took evasive action. Tower advised twin continue to land, with me #2. Made 180 degree and 360 degree for spacing and landed. Several contributing causes to event: told expect runway 34. Tower called king air traffic incorrectly for runway 34, changed my assignment to runway 30 while I was on very short base to runway 34. Heard subject twin call 1 1/2 mi east of navy glenview, but heard no 'clearance to land runway 30' and was not expecting conflicting traffic. Twin had sun in eyes and was very alert to see conflicting traffic -- me. Twin was not on straight-in path for runway 30. 2 times I was on short base -- perhaps committed to landing mentally, and lost traffic awareness. This is very busy airport where often times tower does not clear you to land until on short final. Not a good practice for me (pilot) or tower controller. Perhaps depend too much on tower for spacing awareness and not enough on my (pilot) space awareness.
Original NASA ASRS Text
Title: BE35 AND PA34 HAD LTSS WHEN TWR LCL CTLR HAD BOTH ACFT ON FINAL FOR THE SAME RWY.
Narrative: L BASE FOR RWY 34, #2 WITH KING AIR #1, RPT L DOWNWIND TO L BASE. (KING AIR WAS ACTUALLY R DOWNWIND AND BASE.) TWR ADVISED 'IFR TFC WAITING TKOF ON RWY 34, CHANGE TO L DOWNWIND FOR RWY 30.' FLEW L DOWNWIND AND BASE TO RWY 30. IN POS TO TURN FINAL ALMOST, WHEN SAW TWIN 1 1/4 - 2 MI ON 280 DEG COURSE, APPARENTLY FOR RWY 30 LNDG. WE BOTH TOOK EVASIVE ACTION. TWR ADVISED TWIN CONTINUE TO LAND, WITH ME #2. MADE 180 DEG AND 360 DEG FOR SPACING AND LANDED. SEVERAL CONTRIBUTING CAUSES TO EVENT: TOLD EXPECT RWY 34. TWR CALLED KING AIR TFC INCORRECTLY FOR RWY 34, CHANGED MY ASSIGNMENT TO RWY 30 WHILE I WAS ON VERY SHORT BASE TO RWY 34. HEARD SUBJECT TWIN CALL 1 1/2 MI E OF NAVY GLENVIEW, BUT HEARD NO 'CLRNC TO LAND RWY 30' AND WAS NOT EXPECTING CONFLICTING TFC. TWIN HAD SUN IN EYES AND WAS VERY ALERT TO SEE CONFLICTING TFC -- ME. TWIN WAS NOT ON STRAIGHT-IN PATH FOR RWY 30. 2 TIMES I WAS ON SHORT BASE -- PERHAPS COMMITTED TO LNDG MENTALLY, AND LOST TFC AWARENESS. THIS IS VERY BUSY ARPT WHERE OFTEN TIMES TWR DOES NOT CLR YOU TO LAND UNTIL ON SHORT FINAL. NOT A GOOD PRACTICE FOR ME (PLT) OR TWR CTLR. PERHAPS DEPEND TOO MUCH ON TWR FOR SPACING AWARENESS AND NOT ENOUGH ON MY (PLT) SPACE AWARENESS.
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.