37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1186147 |
Time | |
Date | 201407 |
Local Time Of Day | 0601-1200 |
Place | |
Locale Reference | CHD.Airport |
State Reference | AZ |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Cardinal 177/177RG |
Operating Under FAR Part | Part 91 |
Flight Phase | Initial Approach |
Route In Use | Visual Approach |
Flight Plan | None |
Aircraft 2 | |
Make Model Name | Baron 58/58TC |
Flight Phase | Climb |
Person 1 | |
Function | Pilot Not Flying |
Qualification | Flight Crew Instrument Flight Crew Multiengine Flight Crew Private |
Experience | Flight Crew Last 90 Days 8 Flight Crew Total 780 Flight Crew Type 130 |
Events | |
Anomaly | Conflict NMAC |
Miss Distance | Horizontal 100 Vertical 10 |
Narrative:
My passenger was flying left seat as PIC; and I was sitting in the right seat. Phoenix approach released us from flight following a couple of miles south of sky harbor (phx). I recall on the GPS we were just over 10 miles out from chd at that point. My wife contacted chandler tower; and they told us to enter right traffic for [runway] 22R; so she lined up towards the southwest end of the airport to facilitate a 45 deg downwind entry. We were still high (4;500 ft); so she put the flaps out early to let us descend rapidly without building up too much speed. At about 5 miles out and descending through perhaps 3;000 ft (1.5 miles east of stellar airport P19); a beech baron passed immediately in front of us; right to left on a climbing perpendicular flight path. I estimate it was less than 300 ft in front and 100 ft to the right of us when I first spotted it. By the time I reacted (<< 0.5s) it was disappearing below the cowl; although I grabbed the yoke and banked right; in fact my reaction was far too late to have altered the outcome had the timing been less favorable. I looked out the left window and the baron was rapidly receding; climbing and abeam and then behind the left wing. I estimate we missed impact by approximately 100 ft. At 120 KTS we were traveling roughly 200 ft/second. I suspect it was traveling at similar velocity; climbing out from stellar. Assuming the baron was departing stellar; from the no-wind runway 35; my wife never had an opportunity to see the plane. Once it turned crosswind; it would have been essentially fixed at a right 45 degree bearing; below the horizon; slowly growing and rising. At the instant I spotted it; I estimate it was about 10 ft lower than us but climbing (and we were descending). At all times prior to crossing our flight path; the panel/glare shield would have hidden it from my wife in the left seat. It seems unlikely the other pilot saw us since the baron was level in roll and maintained constant heading while visible to me. I should have spotted it; but instead was preoccupied with monitoring my wife's approach. There was also no warning from the tower. Chandler tower historically has been excellent at providing traffic advisories; but they missed this one (as did I). Perhaps their radar feed from phoenix approach was inoperative. In general; air traffic at the time seemed to be very light. I attempted to acquire additional (factual) information via the internet; but our flight is not recorded; and I was unable to determine how I might find a record of a baron flight at that time/location. As the pilot not flying; I should have spent less time monitoring my wife and more time monitoring the outside. About 30 seconds before the incident; I had spent several seconds scanning stellar for traffic but noted none; and did not look back in that direction until the incident. For single pilot operation; it seems like we might need to institute s-turns for descents. I do plan to equip the plane with ads-B for traffic awareness; but the FAA equipage requirements/constraints have created a practicality conflict (both with what we need/can afford; and what the market currently offers). As noted above; my personal experience has been that chandler tower has been superb at providing traffic advisories. I do note that our regular destinations consistently maintain flight following until we land; handing us off to the tower while keeping the discrete transponder code. Phx has not historically done this; although recently they've done this on some flights; but it has not been consistent.
Original NASA ASRS Text
Title: C177 passenger and rated pilot; reports a NMAC with a BE58 at 3;000 FT just south of PHX. Evasive action is taken; but too late to alter the geometry of the very near miss. VFR flight following had been terminated PHX Approach a few minutes prior.
Narrative: My passenger was flying left seat as PIC; and I was sitting in the right seat. Phoenix Approach released us from Flight Following a couple of miles south of Sky Harbor (PHX). I recall on the GPS we were just over 10 miles out from CHD at that point. My wife contacted Chandler Tower; and they told us to enter right traffic for [Runway] 22R; so she lined up towards the southwest end of the airport to facilitate a 45 deg downwind entry. We were still high (4;500 FT); so she put the flaps out early to let us descend rapidly without building up too much speed. At about 5 miles out and descending through perhaps 3;000 FT (1.5 miles east of Stellar Airport P19); a Beech Baron passed immediately in front of us; right to left on a climbing perpendicular flight path. I estimate it was less than 300 FT in front and 100 FT to the right of us when I first spotted it. By the time I reacted (<< 0.5s) it was disappearing below the cowl; Although I grabbed the yoke and banked right; in fact my reaction was far too late to have altered the outcome had the timing been less favorable. I looked out the left window and the Baron was rapidly receding; climbing and abeam and then behind the left wing. I estimate we missed impact by approximately 100 FT. At 120 KTS we were traveling roughly 200 FT/second. I suspect it was traveling at similar velocity; climbing out from Stellar. Assuming the Baron was departing Stellar; from the no-wind Runway 35; my wife never had an opportunity to see the plane. Once it turned crosswind; it would have been essentially fixed at a right 45 degree bearing; below the horizon; slowly growing and rising. At the instant I spotted it; I estimate it was about 10 FT lower than us but climbing (and we were descending). At all times prior to crossing our flight path; the panel/glare shield would have hidden it from my wife in the left seat. It seems unlikely the other pilot saw us since the Baron was level in roll and maintained constant heading while visible to me. I should have spotted it; but instead was preoccupied with monitoring my wife's approach. There was also no warning from the Tower. Chandler Tower historically has been excellent at providing traffic advisories; but they missed this one (as did I). Perhaps their radar feed from Phoenix Approach was inoperative. In general; air traffic at the time seemed to be very light. I attempted to acquire additional (factual) information via the internet; but our flight is not recorded; and I was unable to determine how I might find a record of a Baron flight at that time/location. As the pilot not flying; I should have spent less time monitoring my wife and more time monitoring the outside. About 30 seconds before the incident; I had spent several seconds scanning Stellar for traffic but noted none; and did not look back in that direction until the incident. For single pilot operation; it seems like we might need to institute S-turns for descents. I do plan to equip the plane with ADS-B for traffic awareness; but the FAA equipage requirements/constraints have created a practicality conflict (both with what we need/can afford; and what the market currently offers). As noted above; my personal experience has been that Chandler Tower has been superb at providing traffic advisories. I do note that our regular destinations consistently maintain flight following until we land; handing us off to the Tower while keeping the discrete transponder code. PHX has not historically done this; although recently they've done this on some flights; but it has not been consistent.
Data retrieved from NASA's ASRS site 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.