Plane Crashes and Incidents

And, it's gone.
As reported on the approach: "touch and go". So it's gone. Or not.

But that's a weird story. First they announced a "touch and go" approach, then requested "high key - low key" landing, approved, which could indicate either a training maneuver or an emergency situation, but in the latter case why intending "touch and go" and no mention of any problem? Then, when reporting low key to the Tower, they also said "gear down" and "low approach"; cleared for low approach. Two minutes later, when taking the last turn toward the runway, they repeated: "gear down, touch and go"; cleared. Some 30 secs later, they performed a text-book belly landing, perfectly aligned, no fire at stop and the crew walked out unscratched.

Very confusing, at least to me with my limited knowledge and understanding, but with this disclaimer my guess would be a training approach with touch-and-go final only the gear down was not successfully executed and no one noticed it.

On the technical side, it looks like the incident might have affected mostly the payload pallets placed under the relatively thin Martin B-57 fuselage:

WB-57 payload.jpg
pallet 1
pallet 1.jpg


Images from WB-57 Payload Diagram PDF, 2021; might have been modified since, but the overall idea has been kept.
So it seems possible that the runway concrete suffered a bigger damage than the aircraft itself, time will tell.

That particular aircraft #927 made a series of test flights in 2021 in preparation for the Summer 2022 deployment (including NASA's Artemis I mission) and was supposed to assist it again in this coming February in the Artemis II mission. The other two WB-57s (926 and 928) seem to be mostly out of service undergoing numerous maintenance procedures and inspections according to available data.

As for its weather related assignment, The ClimateViewer Report does a good job (2024) with many links, if anyone is interested.
 
The High Key position is generally when the aircraft is somewhere over the first third of the runway and is the point at which the pilot will begin his right/left turn and start his descent (if currently level). If it's an actual flame out, then the aircraft may be in a descent prior to reaching High Key but should be attempting to be at or near the altitude that was practiced during a simulated flame out (when training).

The Low Key position is generally abeam the approach end of the runway.

These "Key" positions serve as altitude and configuration reference points in order to ensure that the aircraft will be at the proper position, speed, and altitude over the end of the runway.

"Touch and go" terminology is used during training. On landing, the flap and thrust are set for an immediate takeoff without stopping or exiting the runway.

Touch-and-go essentially joins two manoeuvres into one - the aircraft lands on the runway, then accelerates and takes off again. The procedure is normally practiced during flight training but is sometimes used as a form of aborted landing after touchdown.

There have been several accidents over the years during 'touch and go' landings. During training, several 'touch and go' landings are carried out. In some aircraft, in order to silence the 'to low gear' warning, pilots gave disable this warning and then forgot to enable it, resulting in a 'gear-up' or belly landing! I know of one such accident in my airforce days on an E2C aircraft shown below!

e2c.jpg
 
Last edited:
There have been several accidents over the years during 'touch and go' landings. During training, several 'touch and go' landings are carried out. In some aircraft, in order to silence the 'to low gear' warning, pilots gave disable this warning and then forgot to enable it, resulting in a 'gear-up' or belly landing! I know of one such accident in my airforce days on an E2C aircraft shown below!

That's what I guessed had happened. What is weird though, is that they reported "gear down" to the tower, twice.

Both ABC and NASA claimed a malfunction and emergency landing. Yet there was no sign of the crew being aware of it on the audio recording of their communication with the tower. No request for assistance, nothing.

abc:
A NASA research plane malfunctioned and had to touch down in Texas without landing gear on Tuesday, sliding across the runway on its belly and sending plumes of flame behind it, a video posted to social media showed.

KHOU on twitter:

BREAKING | Video shows a NASA plane making a belly landing at Ellington Airport. Here’s what we know right now.
(linking to the very early video they posted on their YT channel), to which NASA quickly replied:

Today, a mechanical issue with one of NASA’s WB-57s resulted in a gear-up landing at Ellington Field. Response to the incident is ongoing, and all crew are safe at this time. As with any incident, a thorough investigation will be conducted by NASA into the cause. NASA will transparently update the public as we gather more information.

Is it possible that they did everything that was needed to deploy the gear, where certain it worked, yet the gear didn't react, and there was no indication of the failure, and no way for them to not be aware of it to the very end? Or perhaps they realised but decided to focus fully on safe belly landing?

Otherwise, we would be left with forgetfulness classified as a "mechanical issue".
 
As far as I can tell the story blaming a pilot has been there for a week or so now, but indeed it seems to be getting traction. There's no new information though. I agree it's hard to believe someone would kill so many people along with committing suicide.
I find it hard to believe too (re: the June 12th 2025 Air India 171 crash), that someone would chose to commit suicide as well as killing another 259 people, in addition to themselves. However, with mental health issues such as depression, it could be possible. So too, the effects of medications, stress and tiredness combined with distraction.

My question would be, was the action done deliberately? Or unconsciously? I would like to think the Captain (?) didn't end 259 people's lives deliberately. We've all done dumb things when we're tired and distracted. It's just that when a pilot is on "autopilot", the results end up deadly.

Captain Steeeve (video 12.40 minutes) is leaning towards some sort of human interaction with the fuel control switches, because he states that the odds of both fuel switches being faulty, and the pilot who was "guarding the throttles" for take-off's hand slipping and accidentally knocking 2 faulty switches are "astronomical", especially if there was a one second delay before each switch becomes deactivated. Then, 9 seconds went by before the other pilot noticed and the problem addressed.


Then, there is the miracle of the man in 11A, who..... just walked away.....

 
LAX engine fire on a Boeing 787-9 Dreamliner on United Airlines Flight 2127 heading from Los Angeles to Newark, New Jersey.

Passengers aboard United Airlines Flight 2127 were forced to evacuate Monday morning after a reported engine-area fire prompted an emergency landing at LAX.

The Los Angeles Fire Department posted an alert shortly after 11 a.m. confirming that the plane had landed safely.

Sky5 was over the scene less than 30 minutes later, where several travelers were seen standing on the tarmac after the aircraft, which was bound for Newark Liberty International Airport, was evacuated.

Fire officials said everyone made it off the plane safely following the engine trouble. “No patients requiring hospital transport have been identified at this time,” the department said.

The cause of the incident is still under investigation.

Check back for updates on this developing story.


 
A near-fatal collision at Newark Liberty International Airport in New York was avoided by Air Traffic Controllers

Updated: March 20, 2026
  • Alaska and FedEx flights approaching Newark’s intersecting runways
  • Alaska instructed to go around
  • Alaska 737 overflew FedEx 777 as it landed
The NTSB is investigating a “close call” between an Alaska Airlines 737 and a FedEx 777 landing at Newark Liberty International Airport on Tuesday evening. The flights had been cleared to land on intersecting runways when it became apparent to the air traffic controller that the Alaska 737 would not land behind the FedEx 777 as planned. The controller instructed the Alaska flight to go around, with the flight at 300 feet and climbing as it passed over the FedEx flight on the intersecting runway. The Alaska Airlines flight landed safely on its second approach.

Screenshot 2026-03-20 202513.png

FedEx flight FX721, a Boeing 777F arriving from Memphis, was cleared to land on Runway 29. Alaska Airlines flight AS294 from Portland was cleared to land on Runway 22L, which intersects with Runway 29. Planned sequencing indicated by air traffic control audio was for the FedEx flight to land ahead of the Alaska flight. ATC cautioned the FedEx flight of the approaching 737 and informed the crew it would land behind them.

During the approach, it became evident that the Alaska Airlines flight would not, in fact, land behind the FedEx 777 with an acceptable safety margin and the Newark tower controller instructed the Alaska flight to “go around.”

Based on granular ADS-B data received and processed by Flightradar24, the Alaska flight arrested its descent as it passed over I-78 and began to climb shortly after. According to the barometric altitude reported by the aircraft as part of the ADS-B data, the Alaska 737 passed above the FedEx aircraft as it climbed from 300 to 325 feet. Investigators will be able to use data from the aircraft’s radar altimeter to make a more precise determination of the height at which the two aircraft crossed.

I was unable to obtain information regarding this incident at Denver International Airport, and I wonder if it is a case of 4th-density bleed-through.


bafkreiavajsmbtmegjnj3vuxv5ke3zscb6rwapar2z6ozwwhsmn5vbpv2m.webp
 
Back
Top Bottom