Am I missing a thread about this Charlotte overrun?
 

Hey, total lurker here and I'm sure I'm just missing the thread...

Can someone direct me to PPrune coverage for the aa775 overrun in Charlotte?

https://abc11.com/american-airlines-...port/11871132/

Looks like there isn't a thread (well there is one, now :O).

Interesting profile from FR24 - not an overrun, but aircraft appears to have completely departed 18L (all 3 gears on the grass) and then immediately taxied back onto the runway, exited, stopped for just under 15 mins (presumably while being inspected) and then taxied back to the terminal.

Elapsed time from start of roll to stopping on the Twy M/C intersection was 2 minutes, max GS around 39 kts.

Aircraft was back in service 2 days later.

Dave thanks so much for the info..

And it's very rare for me to be involved in a thread this early so I'm going to ask the obvious question...What could cause an aircraft to leave the runway yet be totally airworthy 2 Days later?

​​​Maybe a sticky brake on the side that went off the runway first?

I'd expect it was inspected by a qualified engineer, repaired if required & signed off as serviceable. As to why it left the runway originally, may have had nothing to do with the aircraft; press speculation that is was apparently mechanical doesn't mean it was.

Tyre tracks (aircraft travelling R to L):

Leaving the runway:

https://cimg5.ibsrv.net/gimg/pprune....27c7af7056.jpg

Regaining the runway:

https://cimg6.ibsrv.net/gimg/pprune....9de86d667f.jpg

Source

I would not taxi out of the grass in anything bigger than a 172, and 737>172.

Reminds me of the Britannia Airways Boeing 767 in the middle of night that fully left the runway immediately after landing at NCL/EGNT Rw25, Captain had a brain Aneurysm I think?? Co-pilot took over and got the aircraft back on to runway after around 800m still doing 100kt's+! ATCO in old offset control tower at western end of runway thought the landing looked odd but not sure. Any way the co-pilot as he vacated at the end announced "we think we may have hit a runway light on landing"!! The grass didn't look as good as above and they crossed a fire access track when 'off peste' but hardly made the papers!! Walked the tyre tracks the next morning got the hair on the back of my neck standing!! Here but for the grace of...:)

Eagle-eyed viewers will have noted from the first photo in post #5 that the B738 had drifted to the right of the runway centreline before veering off to the left onto the grass (as confirmed by the ADS-B track).

I don't know whether that sheds any light on the likely sequence of events.

I guess that makes my left brake partial lock up hypothesis pretty unlikely...

And also seems like it's logical that it's reduces the chance of some type of inattention.. if distracted it could make sense to drift off one direction.. but to go in both directions, it seems increasingly likely that there was some type of mechanical difficulty?

The reason I'm curious, is I'm a exGA guy just down the road at RDU and my non-flying friends are bound to ask me about this event sooner or later and I'd like to be prepared to tell them something logical :-)

With that said, with an event this minor, are there any investigations and is it likely that any information will eventually be surfaced?

Numerous press reports of an apparent mechanical problem, no mention as to what the actual problem was.

https://mentourpilot.com/american-ai...way-excursion/
Incident: American B738 at Charlotte on May 19th 2022, temporary runway excursion on rejected takeoff

I would caution that Avherald tends to use a somewhat different definition of a rejected takeoff than the generally-accepted one.

Presumably it will become clear in due course whether an RTO was a factor in the runway excursion or simply a logical consequence thereof.

We need a chicken/egg expert ... :O