My guess would be it's because people like to blame somebody else. If it's a plane then there are large organisations to blame i.e. the airline and the manufacturer. While with cars almost always the blame is with the driver i.e. the people. When it's a manufacturer's fault however nobody bats an eye if they have to recall 500,000 cars to install something that would decrease the risk by 1/10th the amount if everybody uses seatbelts.
Bear in mind that a Boeing 777 like the one that went missing on flight MH370 costs on the order of $200M. You then have potential liability for the passengers (if the airline made culpable/criminal mistakes) of maybe $2-4M per head, for up to 400 pax on a 777 -- they're big (MH370 had only 239 people on board) and you're looking at a billion dollar accident. The airlines and manufacturers thus have a huge incentive not to let this happen again.
(Compare to a car accident: 90% or thereabouts are down to human error, and the vast majority of fatal ones "only" involve a couple of deaths, capping the potential liability two orders of magnitude lower.)
In that sense a large number of people are "affected" (as in likely to click/read the story) if 300 people on a plane die 1000 miles away than 1000 people dying in different accidents over longer period in my home state.
When there is public perception the government and politicians want to step in and want show that they are doing something. That something is more regulations and more checks. That makes air travel expensive and more safe.
You can either have a good team of people drill down into the root causes of a particular mass-transit failure, or you can have them suffer the death of a thousand cuts by investigating every nose-to-tail collision on a highway because people get distracted. One's worth far more to society.
I've read a couple of reports. Quite apart from the issue of saving people's lives, it's good to see the work of someone who someone takes bugs seriously. They never seem to say "let's see if it happens again", "maybe it was a one-off, let's reboot" or "let's upgrade, maybe it's fixed in the latest version".
The report I read most recently described a chain of seven mistakes and other problems, described which ones combined and how, discussed how each of the seven could be prevented and/or made less likely, whether each of the actions was likely to be a net improvement, and finally made recommendations.
IMO, those of us who work with bugs should read one of those reports every so often, just to see/remind us how an unlimited-resources, all-dials-at-11 incident post mortem looks.