Urgent Prayer Request

Over on X, the redoubtable Homer Hickam (Rocket Boys, other books and movies, and a heck of a nice guy I met a time or two when we both worked at NASA MSFC) has put out a request for prayer for the Artemis II crew.

“Just a perhaps unnecessary reminder: The Artemis II crew, as successful as their mission has been, is involved in a dangerous enterprise with a spacecraft that has a heat shield that showed some unfortunate characteristics on Artemis I. If you are prayerful at all, please pray for their safe return to the “fleecy skies and cool green hills of Earth.”

As I put it in a private group elsewhere, they are going to hit the Earth’s atmosphere at roughly 24,000 mph, encounter temps in excess of 3,000 degrees F, and other delights. I’m on record here and elsewhere as suggesting this flight should have been delayed because of problems, the least of which involve the heat shield. The heat shield on Artemis I did indeed display some “unfortunate characteristics” as Homer put it. I am praying and will continue to pray for them. Jon Stokes on X reminded me of this prayer, attributed to Robert A. Heinlein, which I will share:

Almighty ruler of the All,

Whose power extends to great and small,

Who guides the stars with steadfast law,

Whose least creation fills with awe-

Oh grant Thy mercy and Thy grace

To those who venture into space.

By the way, if you know where the quote in Homer’s post comes from, we are friends even if we have not yet met. (smile).

Please do pray for them, as pushing the envelope is always risky. They are a good crew, knew the odds, and cheerfully went forward knowing that what they were doing puts us back on course to the stars. They were and are willing to take the risks to push things forward. Let us pray they get back safe and help us continue to push the envelope. Our future is out there. Never forget: Earth is the cradle of humanity. Children can’t stay in the cradle forever. Time to get moving.

UPDATE I: They made it back safely, and I want to thank all who commented, and special thanks to all those who prayed. I’ve not had time to individually comment on the comments given that the end of Holy Week is quite busy. Know your comments and prayers were and are appreciated. I’m looking forward to some of the post-flight reviews, particularly on the heat shield.

Barksdale And Drones

First, before you do anything else, go read this very good post by Leslie over at Legal Insurrection. She covers a lot and makes a number of very good points. That said, I want to chime in with a few thoughts.

First up, there appears to be some leadership issues. Pete has been fairly clear on the need to develop anti-drone strategies and to be creative in so doing. In fact, some interesting concepts are being tried and actually potentially fielded. Yet, at the same time, the response to a clear and present danger is to monitor, try to jam, and apparently to wring hands and cry how nothing works. Personal opinion, that’s the time to let troops with trap and skeet experience go to work in downing as many as possible.

It would be nice to also to be able to track back the control signals for the drones to determine point of origin. Jamming is well and good, but there’s another phase that seems to be lacking in the response. Fact is, we need robust, capable mobile detection systems that will facilitate a rapid identification of the origin of the signals and allow said site to be neutralized. Ideally, getting those behind the control alive and with equipment intact for analysis, but given that this is a major nuclear base we need to be able to identify and then go in hard and FAST.

Also, question for the audience: Do you think China is the only country or entity that has been buying land near major military installations? If so, why do you think that?

We really do need to rethink the triad and our full posture. We also need to get serious about drones and drone defense, as dithering and hand-wringing is only going to see our aircraft fleet mangled wreckage. Drones require being pro-active, and that is the antithesis of what has been drilled into most military leadership for a while now.

Just some thoughts to share.

If you’ve not been here before, take a moment to scroll up or down, and check out some of my other content. It ranges from my upcoming religious pilgrimage to practical preparedness. Hope you will check it out.

Please check out my Winter 26 Bleg!

Getting hit by lightning is not fun! If you would like to help me in my recovery efforts, and to start a truly new life, feel free to hit the fundraiser at A New Life on GiveSendGo, use the options in the Tip Jar in the upper right, or drop me a line to discuss other methods. There is also the Amazon Wish List in the Bard’s Jar. It is thanks to your gifts and prayers that I am still going. Thank you.

The LaGuardia Tragedy

What happened with the CRJ and the fire truck at LaGuardia was indeed a tragedy, and a preventable one. Not necessarily for the reasons many of the people trying to score political points off the blood of the tragedy are expounding though.

First, let set some basic terms and information that are needed to understand the situation. The FAA and the Transportation Administration control aviation in the U.S. You have flight control, which is the part of the operation that controls and monitors flights in progress. You have departure control which is concerned with takeoff and departure operations. You have landing control, which is responsible for the last part of the flight and landing. You then have ground control, which is responsible for general movement on the ground.

Depending on circumstances, these can all be different people (and some companies even have their own ops people at airports, such as caterers, cargo companies, etc) or they can all be one person. Depends on a number of factors, with the largest being the size of the airport and the amount of traffic. What a lot of people don’t like to talk about is that it also depends on staffing, which started to be an issue in the mid-2000s. There are actually several reasons (no matter what the yard signs say, there are few simplistic problems and no simplistic solutions) and they include training issues, technology issues, and workload.

A lot of this has been discussed in regards the DC crash (covered here, feel free to hit the search button). The technology of the Air Traffic Control (ATC) system is beyond antiquated, as are a number of the collision avoidance systems. In the wake of DC, there was a lot of talk about fixing that right now, and people like Elon and others who know tech volunteered to help. Haven’t heard a word about that since.

Would love an update on what’s being done, or not, and why. There are in fact straightforward solutions using Commercial Off-The-Shelf (COTS) technology that would vastly improve both flight control and approach/departure control. In the past, one of the biggest stumbling blocks was Congress, and some members of the bureaucracy, as such projects did not grease the right hands or flow to the right districts. It would be nice to get a DOGE (or a Data Republican) audit of all that has been pledged and spent on this from 2000 onwards since a lot of it just seems to me to have disappeared.

Congress has also been a huge problem with the staffing issue, particularly the Oklahoma delegation of Congresscritters. Right now, the FAA school for controllers is in Oklahoma; it can’t handle the load it has much less train the numbers of people needed; and, that delegation has blocked every effort to open other FAA schools elsewhere. Just a suggestion, but take your BP meds before you dig into this and other ways Congress has blocked pretty much all efforts to fix the staffing problem.

And it is a huge problem. Controllers, particularly approach/departure/ground, can find themselves working six days a week with mandatory overtime. Before passing judgement, or wallowing in the blood of the tragedy to make points for your side (what ever that may be) check out how long the controller in this case had been working. Check out the last time he had any realistic time off. Now, add in antiquated tech that hinders detection of problems rather than warning of them, and add in effectively what looks to be about three emergency/potential emergencies he’s juggling at once.

This is a life that just ended in most respects. The life he had is gone, and two people are dead and more injured because he was overworked and without help or support from his leadership including Congress. Pray for him, as he is going to need those prayers, even as you pray for the souls of the dead and for the injured. And before you jump on him or to make points, listen to the exchange afterwards, where he says he made a mistake (one he tried desperately to stop BTW) and is comforted by a pilot who told him he did the best he could. And he did, in a system that failed him, and us.

As with the DC crash there is plenty of blame to go around. My ire is focused a good bit on Congress, but more than one administration has not taken transportation, and reform/improvement of the FAA and ATC system seriously. I hope the current administration will take it seriously and that Sec. Duffy will step up and be the leader needed to meet this challenge. He talked good game after DC, and I would like to see some walk to go with the talk. If Congress or others are trying to play their usual games, let’s take the gloves off and do what’s needed before more are killed and more lives destroyed. Again, please do pray for that controller, he needs them.

If you’ve not been here before, take a moment to scroll up or down, and check out some of my other content. It ranges from my upcoming religious pilgrimage to practical preparedness. Hope you will check it out.

Please check out my Winter 26 Bleg!

Getting hit by lightning is not fun! If you would like to help me in my recovery efforts, and to start a truly new life, feel free to hit the fundraiser at A New Life on GiveSendGo, use the options in the Tip Jar in the upper right, or drop me a line to discuss other methods. There is also the Amazon Wish List in the Bard’s Jar. It is thanks to your gifts and prayers that I am still going. Thank you.

Quite A Century

Yesterday was the 100th anniversary of Robert Goddard’s first launch of a liquid-fueled rocket. It literally was two seconds that changed the world.

Today, we have re-usable rockets and regular flights to orbit. Satellites have transformed communications, weather forecasting, intelligence gathering, and more. Research in space is unlocking secrets of the universe, transforming our understanding of matter, and setting the stage for us to get off this mudball and start on our way to the stars (to quote Glenn, “Faster, Please”).

Hard to believe that so much of the modern world started with just two seconds that didn’t even rate a mention in the local newspaper if I remember correctly. Then again, the leading intellectuals (or, at least one: one also wonders if over-credentialed idiots have always been a problem, hmmmm) of the day held forth that rockets would not work in space as there was nothing for them to push against.

I will not knock any of today’s people for they are doing amazing things. That said, they got quite a boost by standing on the shoulders of Goddard, Oberth, and Tsiolkovsky. I even seem to recall one or more members of von Braun’s team talking about what a debt they owed to them during a conversation. Each generation builds upon the previous; yet, there is always a starting point and a starting person. In many respects, when it comes to modern rocketry, Robert Goddard is that man. Salute.

Please check out my Winter 26 Bleg!

Getting hit by lightning is not fun! If you would like to help me in my recovery efforts, and to start a truly new life, feel free to hit the fundraiser at A New Life on GiveSendGo, use the options in the Tip Jar in the upper right, or drop me a line to discuss other methods. There is also the Amazon Wish List in the Bard’s Jar. It is thanks to your gifts and prayers that I am still going. Thank you.

Couple Of Good Reads

Lots going on in the world, but not a lot of time for writing. Besides, why reinvent the wheel when others have already done some very good work?

First up, Francis Turner has a very good analysis of the recent Japanese elections. I’ve been keeping an eye on it, but he is very familiar with things and explains things beautifully. Go read.

Second, Behind The Black has a good post on what I will flat out call a very troubling development at NASA. I’m not happy to read this, and believe it a huge step backwards.

If I come across anything else, will add it here but the day is a busy one and I need to get back to my classwork/homework. More soon I hope.

Getting hit by lightning is not fun! If you would like to help me in my recovery efforts, and to start a truly new life, feel free to hit the fundraiser at A New Life on GiveSendGo, use the options in the Tip Jar in the upper right, or drop me a line to discuss other methods. If you want to know some of what it is going for, read here. There is also the Amazon Wish List in the Bard’s Jar. It is thanks to your gifts and prayers that I am still going. Thank you.

Artemis

I’m actually hoping the upcoming mission slips not just to March, but into April. Not a detailed post, but here are a few highlights.

First, Congress mandated out-of-date tech and other delights to keep certain companies and production lines open (and donations to politicians flowing). Old tech is not necessarily bad: I almost got to co-pilot a Ford Tri-Motor once (lost out to someone with a bit more seniority) and it was a fun and amazing flight. It works, but no one is trying to repurpose the Ford into a hypersonic aircraft, which is not a bad analogy for all the Shuttle-derived tech required by Congress for Artemis.

Second, there have been issues identified — and fixed in record time. Sorry, having worked at NASA as a contractor I’m not fully buying it. If I haven’t already done so, remind me to tell you about how a NASA safety fix that wasn’t tested ended the first tethered satellite system mission pretty much at the start. Short version is that I wouldn’t ride in that capsule. Your mileage may vary.

Third, the tech involved does not do well with cold weather launches. Challenger. That really should be a period dot thing, but…

Fourth, even if you fixed every issue above, Artemis is unsustainable. The price per launch is beyond ridiculous and is a good example why America would be much better off with NASA out of the launch business. Heck, out of the manned space flight business period. NASA needs to focus on it’s stated mission, which is advancing aerospace technology, not trying to do and control everything related to space (and they and certain political leadership seem to like to ignore the whole aviation side of the picture).

I am very concerned that if Artemis launches this month, that there are going to be significant issues potentially up to the loss of vehicle and crew. I hope I’m wrong, and would love to eat crow on this one. That said, there are echoes of Apollo 1 and Challenger for me, and that makes me very concerned.

UPDATE I: Since I wrote this, a fuel leak has pushed the launch into March. A fuel leak in the same area as the first mission. I suspect that April may be optimistic as fuel leaks have been an ongoing issue for three or so years. See this article for more info. More than ever I think Artemis and the decisions behind it by Congress are going to give us another space disaster. One that could easily have been avoided.

Getting hit by lightning is not fun! If you would like to help me in my recovery efforts, and to start a truly new life, feel free to hit the fundraiser at A New Life on GiveSendGo, use the options in the Tip Jar in the upper right, or drop me a line to discuss other methods. If you want to know some of what it is going for, read here. There is also the Amazon Wish List in the Bard’s Jar. It is thanks to your gifts and prayers that I am still going. Thank you.

DCA Almost Final

My apologies for not writing more (and sooner) but I will just say (again?) that the theology course I’m taking is like drinking out of a fire hose. While it will be a few weeks yet before the final report is out on the DCA crash, the items that are going into the report are now released.

I’m going to start with the Safety Data report, which frankly is damning to the FAA and now-former tower management. Short version is that DCA has had problems for years, including the perception that reporting issues would lead to retaliation. There are multiple recommendations in the report for the FAA, and a few for the Army, as leadership at both agencies (and the DoT) was abysmal.

The human performance report is a good overview of the human operations and interactions with onboard technology that is supposed to help prevent collisions. If you want to understand what was happening in each place, the information available, factors that limited the use of technology and prevented adequate warnings, and more, this is it.

The report notes early something I had “seen” early on: the call-out of the CRJ operated by PSA (Piedmont) for American Airlines lacked critical information. There were several planes in the area called out by the controller, and there was no way for the helicopter crew to know which one was being pointed out. There is evidence that they mistook another aircraft for the one they were supposed to be watching. I may not have many hours as a pilot, but every time I had other traffic called out it always specific, as in “you have X aircraft at your Y o’clock high/low/same (altitude). SOP was to locate, then call back and read-back “I have X aircraft in sight at Y o’clock high/low/same” to verify the information.

As a side note, so long as the object was moving relative to you, life was good. It was when things were a dot that you needed to act as the lack of movement meant it was coming straight at you. Therefore you dove or climbed and/or changed course as well. Doesn’t matter if it was a bird (birds can take out a plane and/or pilot) or a plane — by the time it starts to get visually larger it usually is too late to avoid.

There is a lot more in that particular report, and it is well worth reading carefully. As I said earlier, the only people who come out of this pretty much in the clear are the Piedmont crew who were never warned about the helicopter.

Here is the helicopter operations report, and the medical report. On the latter, the controllers on duty that night should have recourse against management for failing to do the proper drug and alcohol tests. While there is no evidence of such, the failure to follow SOP unfairly puts a cloud over them as they have no way to prove they weren’t impaired. On the former, it is worth reading and re-reading. There are a number of issues with Army aviation leadership and operations that need to be addressed. One of which is that a number of the helicopters in the unit involved had altimeters that were/are not giving correct altitude. There’s more, but the altimeter issue is an ongoing major issue that needs to be addressed.

The airplane systems group report is a good primer on ADS-B and collision avoidance — and the limits of technology. This is a good read and I suspect a number of changes may come out of it.

Now, keep in mind that the area around DCA is some of the most congested in the United States. Fact is, there have been a number of efforts to shut down Reagan because of volume, runway length, location, and other issues. Congress has not only prevented closure, but expanded normal operating hours over the expert advice given it simply because it is convenient for them. And make no doubt it is highly convenient. I’ve flown in and out of there more times than I can count because it is right there at the Pentagon, close to downtown DC, etc.

Also keep in mind that there is a lot of military traffic in the area. There have been efforts made to limit military traffic, primarily helicopters, from the area around DCA because of the congestion and safety issues. Those were ignored/overridden on the basis of national security (and convenience as well).

In an ideal world, the helicopter should have been to one side and gone behind the Piedmont CRJ at a safe distance. It should not have been coming up under it as it was landing.

The NTSB has already heavily hinted/indicated that a majority of the blame for the accident resides with the FAA, and I think they are correct. The lack of leadership, poor management (at all levels including the DoT) failed to address a number of issues, technical and human. I would put among them the long-standing failure to upgrade critical systems, a push for DEI over competence in hiring, and other efforts that inhibited recruitment. When you look at all the problems, the FAA failed at every level.

But, there is plenty of blame to go around. I suspect the controllers are going to take a few hits even with staffing/overwork as mitigating factors; and, the instructor pilot in the helicopter is probably going to take a hit or two despite the fact that without an accurate altitude neither he nor the instructee had no way of knowing they were not at the right altitude. Those of you who know aviation also already know that even if the instructee did make one or more mistakes, the failure to correct them (in time) lies with the IP.

As for all the wild speculation that the instructee kamakazied the Piedmont CRJ; that she failed to obey the commands of the IP; that she wasn’t competent as a pilot and shouldn’t have been flying; and all the other junk: the cockpit recorders and radio transmissions (nor her official background) in no way support those claims. In fact, if you look at the voice recordings, it sounds like a fairly typical learning flight. The IP issued guidance as needed, encouraged the instructee, and seemed to have no major issues with the instructee. Yes, the instructee was green in many respects, but that’s sorta the point of doing training flights. And again and again, without accurate altimeter readings in such a congested area bad things are going to happen.

From the reports, along with photos and diagrams released by the NTSB, it is quite possible that the helicopter and the CRJ may not have seen each other until the last second (if at all). The only people who seem to have done everything right and by the book are the crew of the CRJ. When finally did get warning, they did their best to avoid the crash. It is in no way their fault that they were not able to do so.

So, again, I suspect that the FAA is going to get the lion’s share of the blame (deservedly) for failures of leadership and gross incompetence; whether they get called out or not, DoT should catch some of that too; Army Aviation as a whole, along with senior leadership above them, bear a good bit of blame as well; the controllers on duty will be called out; and, it is likely that the IP will take a hit as well. Not named, though they should be, will be Congress who not only continued operations at DCA but expanded them against all informed advice.

Right now, one of my hopes is that the efforts begun in the wake of the crash to finally modernize the FAA systems using Commercial Off The Shelf technology (COTS) are indeed still underway. Elon and some of the DOGE team were providing advice and assistance and I hope his leaving government did not hamper those efforts (which a lot of entrenched interests in DC are opposed to since COTS doesn’t allow for as much graft and power). I also heard that recruiting efforts for controllers and other critical positions had DEI and other hobbles removed and there were a number of people looking to enter the field. Again, I hope that is continuing as it was and is desperately needed.

I agree with the NTSB assessment that this was one hundred percent avoidable. Had FAA management addressed issues and concerns instead of retaliating against those pointing out problems, this would never have happened. If Army aviation and other entrenched interests had not kept the helicopter route open despite strong advice not to, and if they had properly functioning aircraft, this would not have happened. If Congress hadn’t kept DCA open and expanded operations, this would not have happened. I could go on, but what happened is far more the result of an absolute failure of multiple leadership on multiple levels than anything else.

One of the other things I hope does come out of this is improved collision avoidance systems. We need what we have to work, and part of that lies with setting minimums and standards for lower altitudes. We need newer systems that can and will integrate and operate as noted in the report(s). We also need to be sure military and civilian systems will interoperate, especially in areas such as DC and DCA where there is heavy traffic in close proximity. Again the reports make some good points on that.

I hope some good can come out of this tragedy. I also hope that the final report, along with these reports and previous releases, will put to rest the unfounded and reprehensible speculations of a deliberate crash and/or an out-of-control helicopter trainee.

Getting hit by lightning is not fun! If you would like to help me in my recovery efforts, and to start a truly new life, feel free to hit the fundraiser at A New Life on GiveSendGo, use the options in the Tip Jar in the upper right, or drop me a line to discuss other methods. If you want to know some of what it is going for, read here. There is also the Amazon Wish List in the Bard’s Jar. It is thanks to your gifts and prayers that I am still going. Thank you.

Louisville Crash Preliminary

Just saw the preliminary report from the MD-11 crash in Louisville (Main Page, Preliminary PDF). As for the cause, no surprise but want to go back and check one thing on maintenance before commenting on such.

One thing I can say is that I expect this will end the use of MD-10/MD-11 planes in the U.S. The issues with the pylons and attachments are ongoing and it is not clear that even aggressive inspection and maintenance will be sufficient. Or, rather, it is going to be costly to operations. It’s also more than the direct costs: it is going to be insurance, litigation (and threats thereof), and public relations in regards continued use.

That said, it will be interesting to see what comes out of the testing being done at the National Transportation Safety Board (NTSB) labs. A soft landing in this case might be a recommendation by the NTSB that the 10/11 be retired, which the FAA could then make a directive. This could allow various insurance and other protections to proceed.

In a way, it’s a bit sad. The plane (s, I am referring to the 10/11s as one) has been a wide-body heavy workhorse, though with some stigma. A lot of that came from the 3-engine design of it and the L-1011 TriStar. Both were advanced aircraft in terms of technology, and there were some accidents that resulted in the public being wary of them at first.

I seem to remember a movie being made about the L-1011 crash in the Everglades that brought up the story that the ghost of one of the crewmembers killed in the crash was reported to have said that there would never be another crash of a L-1011. If a ghost did say that (great TV and propaganda, not so sure it’s real history) they were wrong, but it was many years before there was another crash.

The crash in Louisville is very similar to the crash in Chicago a number of years back. Same engine involved, similar pylon issues though that one was blamed on using forklifts to remove/replace the engines if I remember correctly. From what I was reading in the preliminary, I really think the metalurgical tests are going to pretty well make or break the future of the plane.

I have flown as a passenger on the L-1011 and the DC-10 (not sure about the 11), and have both loaded and done pushback on cargo DC-10 & 11s. So glad to do pushbacks with a batmobile versus a tug, as they truly are heavies (esp. loaded). This made using a tug not particularly fun, whereas the batmobiles would pick up the nose wheel and made pushing and turning a breeze (and even fun).

The three-engine widebodies had range and capacity. They filled a particular niche in cargo operations that can be covered but not necessarily fully replaced. For certain routes and operations, they really were the best choice.

That said, I’m not sure the pylon issues can be overcome. Even if they can, how insurers and others react to them continuing to be used is going to drive a lot of decisions. Air transport is costly enough as it is. If insurance and other costs go up too much, the planes will be gone even if a way is found to keep them flying. If I were in an air cargo C-suite right now, I’d be looking at my options very carefully and with an eye towards moving away from use of the 10s-11s.

Nor is it necessarily a loss to the air cargo companies. It is not uncommon, as I understand it, for those companies to buy the planes, then sell them to an outside company, who then leases the plane back to the air cargo company who then operates it including basic maintenance. Yes, tax laws and regulations are the big reason for this (again, as I understand it). Now, if I were the company that actually owned the plane, I’d be looking at options and for an overseas buyer.

And, yes, I am still monitoring the NTSB investigation into the DC crash (main page). The transcripts of the radio and internal coms is interesting. I’ve got my suspicions on what happened and what is likely to be in the final report. That said, still not jumping in as I may have missed something. I do think closing that corridor was long overdue. I am also still waiting for the final on the air ambulance crash as well.

More soon.

Getting hit by lightning is not fun! If you would like to help me in my recovery efforts, and to start a truly new life, feel free to hit the fundraiser at A New Life on GiveSendGo, use the options in the Tip Jar in the upper right, or drop me a line to discuss other methods. If you want to know some of what it is going for, read here. There is also the Amazon Wish List in the Bard’s Jar. It is thanks to your gifts and prayers that I am still going. Thank you.

Jared Issacman: YES!

I am beyond happy that Trump has re-nominated Jared Issacman to lead NASA. It is well beyond time, I don’t think his original nomination should have been pulled in the first place, and the fact that so many in the space-industrial complex are unhappy fills me with great joy.

If you haven’t worked there, it is almost impossible to describe the mess that is NASA. It went from “Can-Do!” to “Can’t Do” with increasing layers of risk-averse management in an amazingly short time. Almost any hint of failure, or the possibility of failure, would get good ideas and programs cancelled. Think I’ve already told the story of the Tethered Satellite System, but it is a classic example of zero-sum safety run amok (the loss of Challenger being different but resulting in the loss of life).

NASA has strayed so far from it’s official and core mission it’s not funny. It’s one reason I’m glad to know that there is already some form of “Athena” (and love the leak as they leaked a Canary Trap). NASA should not be in the launch business (never should have gotten this far), nor should it be the single-route into space on any level.

Issacman is the single best shot we have for saving NASA from itself and those growing rich off it’s indulgences. It needs “Athena” in a big way, as that is the way to ensuring the future of humanity, and that humanity has a future. One can only hope that for once, Congress will move quickly and decisively to get him into position. It can’t happen soon enough.

Also, if he happens to read this, I hope he will move on the necessary research to ensure humanity can reproduce in microgravity and, to quote Bugs Bunny, GET US OUT OF HERE!

Getting hit by lightning is not fun! If you would like to help me in my recovery efforts, and to start a truly new life, feel free to hit the fundraiser at A New Life on GiveSendGo, use the options in the Tip Jar in the upper right, or drop me a line to discuss other methods. If you want to know some of what it is going for, read here. There is also the Amazon Wish List in the Bard’s Jar. It is thanks to your gifts and prayers that I am still going. Thank you.

Another Old Memory

Again, X strikes again. In response to a post on X, I remembered the time a group of unsuspecting passengers participated in a mock carrier landing with a 747.

My go-to airline used to be Delta, and the second time I worked for NASA I usually made Platinum-level frequent flyer by March of each year. Domestically, Delta at the time was very good. Other than some issues with things being stolen out of luggage (and oddly enough one time returned), things went fairly well.

Internationally however, I had a huge issue with the fact that one of their major partners was Air Chance, aka Air France. There was a chance the flight would not be cancelled, there was a chance it would take off on time, there was a chance it would arrive on time, and you get the picture. It was also a given that Air Chance would lie to your face about any number of things.

I will give them credit for one thing: they knew they were lying and while they didn’t really care, they had a unique way of dealing with the customer service issues. After having been lied to about arriving on time; about having my connecting flight delayed for us on it; and, about a few other things, I and others were put aboard a later flight to the same destination. Pretty much the entire plane was filled with passengers who had been lied to and delayed. The flight crew came down the aisle with carts full of wine and booze. Pick your bottle, shut up, and be quiet we are not going to deal with it. By the time we landed, we may have been still PO’d but we didn’t care. Amazing what a bottle of good cognac will do to help you cope with the unchangeable. I will say that from then on I told the transportation people to not put me on anything Air Chance and have avoided them like the plague.

Which brings me to the story seen above. The flight was supposed to be Delta, but was (of course) Air Chance. We did the trans-Atlantic bit, came into land, and for some odd reason the pilot decided to re-enact a carrier landing. Now, to be fair, I’m not sure that’s accurate as there are several other possible reasons he decided to land on the overrun and stop the plane before the first cross taxiway. Not sure what those could have been (chemically induced perhaps?) but there may have been a reason of which I am not aware.

Had it been a real carrier, I’m pretty sure we would have hooked the first wire. Seriously, I think we hit on the overrun. We hit hard and we braked hard. Not entirely joking that we could have stopped on a carrier deck. To say the plane made odd noises is an understatement. We stopped. We stayed stopped for about ten minutes at a very busy airport.

When we moved, the plane made VERY odd noises and parts of the plane did not appear to move in unison. During our sitting phase, I had already made a mental bet we would have to be towed in. Still amazed we were not. As it is, with a mechanical cacophony, we eventually made it to international arrivals. I heard later that the plane was then towed (with no passengers or other witnesses around) to maintenance.

That was almost as much fun as the time we passed the abort point on takeoff and were still on the ground. Different flight, but another time I thought we were going to make the news in a bad way… Remind me and I will tell that tale one day.

Getting hit by lightning is not fun! If you would like to help me in my recovery efforts, and to start a truly new life, feel free to hit the fundraiser at A New Life on GiveSendGo, use the options in the Tip Jar in the upper right, or drop me a line to discuss other methods. If you want to know some of what it is going for, read here. There is also the Amazon Wish List in the Bard’s Jar. It is thanks to your gifts and prayers that I am still going. Thank you.