Sie können uns dabei helfen, FlightAware weiterhin kostenlos anzubieten, indem Sie Werbung auf FlightAware.com zulassen. Wir engagieren uns dafür, dass unsere Werbung auch in Zukunft zweckmäßig und unaufdringlich ist und Sie beim Surfen nicht stört. Das Erstellen einer
Positivliste für Anzeigen auf FlightAware geht schnell und unkompliziert. Alternativ können Sie sich auch für eines unserer
Premium-Benutzerkonten entscheiden..
What I did hear, though, was on the very first attempt to land, the tower controller getting a bit impatient that the traffic *behind* was closing fast, and possibly the SR20 didn't get down fast enough; so the Tower calls the SR20 off in order to make room for SW235 to land without having to go around.
I'm not sure, but my sense is that the FARs say the lower-altitude traffic has priority on landing, but obviously a controller can alter that. However, this could have been the first link in the accident chain. I don't know whether the SR20 could have landed long (assuming she was on a high approach), but rwy 4 is 7600' long, so there's a chance that had SW235 been sent around, the SR20 could have landed safely, eventually, on rwy 4, and the rest of the story would not have happened.
Next, there seems to be confusion on the (first) go-around. The tower puts the SR20 into a right downwind for rwy 35, which makes sense, but then the controller issues a "turn left heading 30 degrees" for some unknown reason, taking the SR20 away from the 35 pattern. Then, a second controller comes on and offers her to follow a 737 to rwy 4, which she would like. But it seems she is now headed AWAY from the airport, but given clearance to land on a runway that is both behind her and in the same direction as she's now heading. Which means a full 360-degree pattern to get back to it.
More confusion on the radio (about which right base the tower wants her on, if any??), and the now-exasperated Second Controller clears her to land on 35. It sounds like this would work out (I can see it on paper), but her next call is "I don't believe I'm lined up for that [rwy 35]". Which confuses me now, since I can't tell what's she's lined up for. Then the (Second) controller sends her into a right turn to about 040 which again would take the SR20 away from the airport.
A few moments later, the Tower gives the SR20 a right turn back to 35, and tells another plane that the SR20 is on a one-mile final. So all this maneuvering is happening in a small area... But this approach is evidently high, according to the tower, so he calls the missed and the SR20 goes around again. Rwy 35 is 6000 feet long, so perhaps all the maneuvering was done too close to the field -- i.e., the tower should have waited for the SR20 to fly a bit further out before coming back around to land this time.
For the next approach, we hear that the SR20 is cleared again onto 35, even though the tower says there's no traffic on rwy 4 (which would have been better given the winds). Another link in the accident chain??
Then the SR20 misses 35, sounds like she was high this time, and the controller gives a left turn back to the rwy 4 downwind, and he's advising her about the traffic situation for rwy 4, and in the middle of it there's the "Straighten up, straighten up" call, and that's the end.
Through it all (except for maybe this last turn), the SR20 pilot sounds composed and in control of her airplane, given all the stuff going on around, the traffic calls, and the changes in plan. I don't get the sense that she's too low-time for the work at Hobby, and certainly she's not daunted by landing with big iron around nor overwhelmed by the controllers at a major airport. Something else must have gone wrong here -- fuel starvation? stall-spin at a low airspeed while maneuvering in close?
I don't know, but this seems to me an accident that shouldn't have happened and one from which we can all learn a lot.