Another week, another Cirrus crash

Sad to hear. And it will interesting to find out what happened.

I don't know the specifics on the CAPS, but I know you can't (aren't supposed to) pull it below a certain altitude. Since it appears he was coming in to land, he may have been too low for the CAPS.
 
Weather went low IFR right around the time of arrrival. The flight track looks like he went off autopilot around the FAF and became completely disoriented. Multiple heading and altitude oscillations, including 4,000 fpm up and over 7,000 fpm down in the last descent.
 
Recreational IMC, it's an equal opportunity killer. A recurring modality, one day they'll outlaw it.

For now, I'll still defend the people's right to die in the name of recreation. If society can stomach the sheer levels of automotive carnage and shrug their shoulders because it's a majoritarian activity, then they can spare me a few hundred winged lawnmowers a year coming from together for the amusement of the minority.
 
There was a cold/stationary front right over the airport at the time of the accident. Lots of low clouds associated, with some smaller and several larger, strong convective cells popping nearby, mostly to the east, around Monroe. However, a broken line of broken, smaller, lighter showers had started showing up on radar, passing by the FAF right around the time of the apparent loss of control. Echo tops to the south of the airport were generally around 5-10,000’, with some to 20,000 a few miles farther south. Some of these were more elevated in nature than others.

A convective SIGMET was valid for that area and was renewed just after the accident time.

The closest TAF at KMLU, issued at 1140Z, called for the following (accident sequence was from 1441 to 1442Z):

FM211300 25006KT P6SM VCSH OVC15
FM211500 35003KT 4SM SHRA VCTS OVC015CB

Weather depiction charts showed the arrival of the front, the potential for low clouds and thunderstorms. The issue may have been the timing of the frontal passage, which is not always easy to predict.

With daylight breaking, combined with the arrival of a slow-moving front, there was definitely potential for increasingly poor, unpredictable weather. Not to say this is what caused the accident, but it’s a reminder that it’s easy to get lost in the weeds of specific observations and forecasts for a small area (especially TAFs and METARs) and try to squeeze in geographically and/or by timing. But we also potentially miss the bigger picture of what’s causing the weather and how that’s trending and ultimately affecting the area.
 
I think you could just as easily write "another week another brand x crash". Think we just automatically assume Cirrus equals pilot who's checkbook exceeds their skills. True in some cases and not in others. Same as any other plane.
 
Stop letting George do all the flying all the time.

For those of us that learned to fly instruments in old airplanes, without even a standard six-pack, it seems amazing someone can get so disoriented with a big 10 inch color display of the horizon right in front of you. My guess is he became so enamored with trying to reprogram the autopilot/FMS while hand flying, he wasn't paying attention until his inner ear started screaming. His best bet would be to forget the autopilot, focus on the PFD to get wings level, preferably in a slight climb, and get reoriented. Tell ATC what's going on and let them get you on a heading and altitude to get yourself sorted back out.
 
The fun of having an ancient autopilot is not trusting the thing anywhere near the ground.

In my case, the original Century 31 A/P too often failed miserably in Approach Mode, in IMC conditions somewhere around the IF/IAF or FAF. On the plus side, it was a great training device teaching instant comfort with A/P disconnect and reversion to hand-flying before things got scary.

After spending around 15K over 5 years of unsuccessfully trying to obtain a semblance of reliability, ended up installing an S-Tec55, and never looked back....
 
Last edited:
Back
Top