Incredible what is possible when no alternative is available.

Yeah, almost close enough to leave tire marks on the top of the other plane.

I thought this would have been a bigger story.

Would TCAS be alerting for that? I would assume so..

Svandamme,

A windmill taxi is/was the preferred method for KC-130s over a buddy start. Both procedures required taking off the busted starter to keep FOD from damaging things.

A windmill taxi start required a minimum of 7,000' and looking at other performance parameters. The not to exceed speed was 100 KIAS. Basically a planned and briefed high speed abort with a couple differences; engine to be started had it's blades set a specific angle then power set at flight idle, symmetricals to full power and feed in non-symmetrical power with rudder effectiveness and start retarding power no later than 80KIAS, start pulling symmetrical power at 90KIAS to not exceed 100 KIAS. The Co-pilot and FE monitor the engine start and the FE adjusts power to keep it out NTS (Negative Torque Signal).

In the USMC VMGR syllabus this was introduced and performed at a co-pilots first T2P check ride and again in the Aircraft Commander upgrade syllabus with a greater depth of knowledge on systems and being the QA on the maintenance requirements.

Basically a non-event.

S/F, FOG

Here is actual video of FedEX

https://twitter.com/documentingatx/status/1623745063388958720?s=51&t=lqP19zCaLLI0y_MU3ua71A

CGI recreation, but scary none the less. I think the FEDEX crew were completely shocked when the SW aircraft pulled on the runway. Waiting to chat with a close friend who is a senior check pilot of FEDEX to get his take. Appears as if tower hosed this up as bad as you can, but the SW pilot should have looked out his window and seen the FEDEX heavy on final and not blindly followed takeoff approval. As always, not worth speculating until the investigation concludes...

^^

I thought I read there was dense fog at the time of the incursion but I could be mistaken. Still a blunder on the controllers part.

Dense fog and fedex was on an autoland approach with no minimums. Great s/a by the fedex crew averted a tragedy. Controller likely assumed sw was going to do a rapid depart and they didn’t


Sent from my iPhone using Tapatalk

http://forums.pelicanparts.com/uploa...1676158699.jpg
http://forums.pelicanparts.com/uploa...1676158699.png

http://forums.pelicanparts.com/uploa...1676159220.jpg
http://forums.pelicanparts.com/uploa...1676159220.jpg
http://forums.pelicanparts.com/uploa...1676159220.jpg
http://forums.pelicanparts.com/uploa...1676159220.jpg
http://forums.pelicanparts.com/uploa...1676159220.jpg
http://forums.pelicanparts.com/uploa...1676159220.jpg
http://forums.pelicanparts.com/uploa...1676159220.jpg
http://forums.pelicanparts.com/uploa...1676159220.jpg

Fedex: "Fedex cleared to land"
Tower: "Cleared to land"
Tower: "Southwest cleared to take off" (SW just heard last and didn't question)
Tower: "Traffic 3 mile final is a heavy 767" (both Fedex and SW hear this. Fedex does not correct.)
Fedex: "Tower confirm cleared to land"
Tower: "Confirmed"
Tower: "SW confirm on a roll"?
SW: "We're on runway now"
---Fedex breaks through fog at 500ft, sees plane on runway, and aborts---
Tower: "SW abort" (they didn't say Fedex)

3rd high altitude object shot down by F22 over Canada


I have a sneaking suspicion the F22 community is ordering them on Aliexpress to get their killratios up.

They probably pitching in now to order a set of 5 to get an Ace in a Day deal



thx!

I think fed-ex told sw to abort.

Yes, they did... Great SA by the FedEx crew to be aware this might be an issue before it became too late. SW is known for fast taxi, cutting lines, rapid departures etc. If they would have taken off in a expedited (timely) manner like they usually do, probably would not have been an issue.. That being said, the controller should not have done that on an IMC day.. On a clear day, with the same scenario, the FedEx crew would have gone around much earlier and would have a lot more space between them, or the SW plane would have done a "normal" fast departure and no issue with spacing.

If it was that sort of weather where a CATIII autoland was being executed, the SW should have been nowhere near the runway as the protected area is large for that sort of approach.

Correct. One of many issues.

All Things Aviation Related
 

Have I ever mentioned how much I love Flightaware? https://uploads.tapatalk-cdn.com/202...ad0a5d0483.jpg

Very interesting.

Back of the Frigate, all tucked in:

http://forums.pelicanparts.com/uploa...1676576686.jpg

<iframe width="930" height="523" src="https://www.youtube.com/embed/EsxiRdQPUvI" title="Crazy Crosswind Landings &amp; Ground Loops | Oshkosh EAA AirVenture 2022" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" allowfullscreen></iframe>

Anybody read about the flight leaving Hawaii? I got up to about 3000 feet and dropped fast to about 800 feet. No cause mentioned, but the pilots are scheduled for extra training.

What happened?

Speculation from pilots on the web is a severe downdraft. The pilots likely got the extra training b/c they overloaded the plane g wise on the recovery-g limit is 2.5 and they hit 2.6, requiring an expensive inspection.