@@KRAVECRAVER1270 ..AND YOU AREN'T PERFECT. You can't "easily"break the gear in TFS,it need to be fast,And if I was too fast and broke the landing gears,I can't do the bounce,And if I hiit the ground at that speed it will be ruin. So sh-t the f-ck up. I'm tried of every sh!t comments. Do it then,If you think you are good.
Song: Young girl a edit OMG how do i get 2 reply Edit again making story FedEx Express Flight 80 was a scheduled cargo flight from Guangzhou Baiyun International Airport in the People's Republic of China, to Narita International Airport in Narita, Chiba Prefecture (near Tokyo), Japan. On March 23, 2009, the McDonnell Douglas MD-11F (N526FE)[1] operating the flight crashed at 6:48 am JST (21:48 UTC, March 22), while attempting a landing on Runway 34L in gusty wind conditions. The aircraft became destabilized at flare and touchdown resulting in an unrecovered "bounced" landing with structural failure of the landing gear and airframe, and came to rest off the runway, inverted, and burning fiercely.[2][3] The captain and first officer, the jet's only occupants, were both killed.[4] FedEx Express Flight 80 The wreckage of FedEx 80 Accident Date March 23, 2009 Summary Crashed on landing due to bounced landing caused by fatigue Site Runway 34L on Narita International Airport, Narita, Chiba Prefecture, Japan 35°45′35″N 140°22′40″E Aircraft Aircraft type McDonnell Douglas MD-11F Operator FedEx Express IATA flight No. FX80 ICAO flight No. FDX80 Call sign FEDEX 80 Registration N526FE Flight origin Guangzhou Baiyun International Airport, People's Republic of China Destination Narita International Airport, Japan Occupants 2 Passengers 0 Crew 2 Fatalities 2 Survivors 0 Accident edit After making an approximately 1,800-mile (1,600 nmi; 2,900 km) overnight flight from Guangzhou, China, the air crew made an early morning approach to Narita Airport outside Tokyo.[5] Other traffic landing just ahead of the accident aircraft reported "wind shear" at an altitude of under 600 meters (2,000 ft)," and this information was relayed to the FedEx aircrew.[3] Surface winds at the time of the accident were reported from 320° at 26 knots (30 mph; 13 m/s; 48 km/h) gusting to 40 knots (46 mph; 21 m/s; 74 km/h).[6] After making a hard landing on runway 34L, the plane bounced three times, coming back down on its nose gear first (a condition called "porpoising") resulting in the loss of directional and altitudinal control. The left wing struck the ground as the gear failed, causing the aircraft to veer to the left, burst into flames and invert as the airframe broke up, and came to rest upside down in the grass to the left of the runway.[2][3][7] It took firefighters about two hours to extinguish the blaze, which completely destroyed the aircraft and its contents.[7] Fatalities edit The only people on board the aircraft were the Captain, Kevin Kyle Mosley, 54, of Hillsboro, Oregon, and First Officer Anthony Stephen Pino, 49, of San Antonio, Texas.[4] Both pilots were removed to the Japanese Red Cross Narita Hospital (成田赤十字病院 Narita Seki Jūji Byōin) where they were pronounced dead. Captain Mosley, a former United States Marine Corps (1977-1983) fighter pilot, had been with FedEx Express since July 1, 1996 and had accumulated more than 12,800 total career flight hours, including 3,648 hours on the MD-11.[8] First Officer Pino, a former C-5 Galaxy pilot in the United States Air Force (1981-2004), joined FedEx Express in 2006 and had accumulated more than 6,300 total career flight hours, 879 of them on the MD-11.[4] Nobody on the ground was injured. Runway closure edit Runway 16R/34L (length 13,125 feet (4,000 m)) was closed for many hours after the accident (with passenger flight cancellations or delays), leaving the shorter 16L/34R as the only available active runway.[9][10] As a result, many flights operated by larger aircraft had to be canceled or diverted to other airports such as nearby Haneda Airport, as 16L/34R is too short (length 7,150 feet (2,180 m)) for some types to operate safely, and some large aircraft types such as Boeing 777-300ER and Airbus A340-600 are restricted from using taxiway "B" (Bravo) which services that runway because of inadequate horizontal clearances.[11] Aircraft history edit The aircraft involved in the accident, photographed two days before the accident at the same airport. The aircraft involved when still in service with Delta Air Lines. The aircraft was built in 1994[12] as an MD-11 passenger airliner. It was acquired temporarily by NASA to use as the test bed for their Propulsion-Controlled Aircraft system (PCA) in 1995.[13][14] Later it was owned and operated by Delta Air Lines from 1996 to 2004 under the FAA registration N813DE in such configuration.[15] The trijet was sold to FedEx in October 2004 when Delta retired its MD-11 fleet in favor of switching to more-efficient twin-engine Boeing 767s and Boeing 777s on its long-haul routes. Following its acquisition by FedEx, the plane was stored at Phoenix Goodyear Airport in Goodyear, Arizona[16] pending its conversion there to an MD-11F by Dimension Aviation, Inc.[permanent dead link], Boeing's Douglas Products Division airframe conversion contractor located at that field. The aircraft entered service with FedEx in its all-cargo configuration in late 2006 as N526FE. It was powered by three Pratt & Whitney PW4462 engines.[17] Cause edit Learn more This section needs additional citations for verification. (March 2016) The Japan Transport Safety Board (JTSB)[18] dispatched six investigators to the airport.[19] The United States' National Transportation Safety Board (NTSB) sent a team to Japan to assist with the investigation.[10][20][21] The crash was FedEx's second fatal accident involving a jet aircraft, following the loss of a FedEx owned B747-249F that crashed February 18, 1989, near Kuala Lumpur, while still painted in the Flying Tigers livery after the acquisition of the Flying Tigers Line by FedEx in December 1988. This was the first fatal accident at Narita Airport.[1][10] The accident was attributed by the JTSB to a series of "porpoising oscillations" that developed during touchdown,[22]: 97 following a high sink rate during the final approach. The first officer executed a late flare, in which sink rate was not suppressed until the plane was nearly on the runway, but which also would minimize "float" that might carry the plane further down the runway and reduce its safe stopping distance, or carry it off the centerline in the existing crosswinds. This high touchdown sink rate, coupled with large nose-up inputs, caused the first bounce. A large nose-down input was applied, causing a touchdown on the nose gear. This deviates from approved procedures for the MD-11 during a bounce, which specifies the pilot is to hold a pitch angle of 7.5 deg and use thrust to adjust the descent rate. The plane bounced off this second touchdown, pitching upward. The large control inputs by the first officer resulted in a hard touchdown on the main landing gear. This final touchdown was hard enough (1,200 ft/min (370 m/min)) to cause the left wing to fail as the left main landing gear transferred force up into the wing, exceeding its design limit. The JTSB report suggested the fire might have been averted if the landing gear fuse pin had failed as designed, but that much of the touchdown force was horizontal to the pin rather than vertical, keeping it intact. The report also cited the crew's use of autothrottle during landing despite gusty wind conditions.[citation needed] As a result of this accident the Japan Transport Safety Board published its final report on April 26, 2013, in which it made a number of new safety recommendations including that "in order to reduce the occurrence of MD-11 series airplanes' severe hard landing and bounce in which an overload is transferred to the MLGs and their supporting structure, the Boeing Company should improve the controllability and maneuver characteristics by improving the LSAS (Longitudinal Stability Augmentation System) functions, reducing the AGS (Auto Ground Spoilers) deployment delay time and other possible means. Possible improvement on LSAS functions may include: a function to limit large nose-down elevator input during touchdown phase, which is a common phenomenon in severe hard landing cases accompanied by structural destruction for MD-11; and a function to assist bounce recovery and go-around in case of bounce. In order to help pilots to conduct recovery operation from large bounces and judge the necessity of go-around, studies should be made to install a visual display and an aural warning system which show gear touchdown status on MD-11 series airplanes."[22]: 97 The investigation into the two pilots' performance during flight 80 found that both exhibited signs of lack of sleep and fatigue, and the first officer was heard on the cockpit voice recorder talking about how he had not slept very much prior to operating the flight.[22]: 14 A look at both pilots' activity in the days leading up to the flight found that, based on accounts from hotel staff, credit card transactions, and other signs of activity, neither pilot could have had more than four hours of consecutive sleep in the twenty-four hours leading up to the crash.[citation needed] Additionally, the pilot flying, First Officer Anthony Pino, usually served as a relief pilot, taking control in the middle of long-haul flights. He therefore had little experience in landing the MD-11, and performed landings very infrequently.[citation needed]
Bagi yang belon tau itu pilotnya capt kevin kyle. Mosley dan telah mekumpulkan total jam terbang 8.132 umurnya 54 dan fo anthony stephen pino telah mekumpulkan jam terbang 5.248 umurnya 49 saat kecelakaan saat 23 maret tahun 2009 dari guanzohou ke tokyo oo iya itu pesawat kargo pesawat saat jam 1 ini terbang normal selai terbang nya kira kira 3jam 26 menit dan cru dari fedex ini mulai berkomukasih sama menara control petugas control pun angin di runewe lalu roda pun di turun kan namun teryata pesawat itu megalami turbo lenci 2 kali tanpanya ada peringatan ketika roda pesawat pertama kalinya menyentuh daratan runewe pesawat ini langsung meluncur dan bagian belakang pesawat ini terbakar dan pesawat bener bener tidak stabil pesawat kemudian terbalik hingga sayap sebelah kirinya patah pesawatnya terbakar dan terus terseret 9 meter petugas e tisi yang melihat kecelakaan langsung menyalakan alamem lalu pemadam kebakaran langsung evokuasi dan 2 pilotnya wafat selesai 😢😢😢
The last words were YEEHAW RIDE EM COWBOY but the SHIT SHIT SHIT want the last words cause as you can see when the plane was upside down the pilot was still talking last words but he was supposed to be dead when the plane was upside down
The aircraft became destabilized at flare and touchdown resulting in an unrecovered "bounced" landing with structural failure of the landing gear and airframe, and came to rest off the runway, inverted, and burning fiercely. The captain and first officer, the jet's only occupants, were both killed.
CVR: GPWS: 1000,500 Cap:I told you what to do Cap:clear to land 24L Cap:stable *Firsts touch down* Cap:shiiiiiiii *Second touch down* Cap:shiiiiiii hehehehe GPWS:30,20,10 *Third touch down* *Crash* END
Context:Every times I checked my comments It's always hurt. (Nothing to expect this comment there always be a HATER who's ruining other feeling. I'm serious.)
Game graphics The game is fit for mobile if you have high graphics it'll be unplayable you need a high end phone to play this but most people might have old phones so the game dosent need good crash it'll just break into pieces that's why there's no fire
Here is the cvr: GPS: 500 plot: clear to co pilot: land 34L steble GPS: 30 20 10 pilot: shiiiii heheheaha bonce X3 *sound of crashing* rip to the pilot rip and co pilot):
![ไลฟ์สุ่ม iPhone 295 บาท... โกงมั้ย?[ โกงมั้ยครับ ep.97 ] | DOM](http://i.ytimg.com/vi/gdstHEE4UUE/mqdefault.jpg)
Damn, that is the best fedex 80 recreation in tfs I’ve ever seen, props to you
Dude that's fedex flight 80 feel bad for the pilots that died on fedex flight 80
@@tim0409-c5oWilliam_William just say the recreation is cool not the real crash
😭😭😭😭😭😭😭🥹🥹🥹😚🥹😚🥹😚🥹😚😚😚😚😚😚😚😚🥰🥰🥰🥰🥰🥰🥹🥹🥹🥹🥹🥹🥹🥹🥹🥹🥹🥹🥹🥹🥹🥹🥹🥹❤️❤️❤️❤️🩵🩵🩵🩵🩵🩵🩵🩵🩵🩵🩵💚💚💚💚💚💚💚💚💚💚💚💚💚💚@@tim0409-c5o
😱😀
@@tim0409-c5onobody died I think
R.I.P FedEx flight 80.
We will miss you.
Song؟
@@adrock_sokolov6570Young Girl A
Why when ppl recreate crashes its always FED EX 80a
@@Thanyaprat20773no it named young girl a
@@Thanyaprat20773 no its call young girl a
“RIDE EM COWBOY”
Famous last words…
Wmmdn❤❤❤❤
@@anna_silva18Is bro a 5 year old?
No don’t argue@@Nahjittrippin6969
"Sh*t! Sh*t! Sh*t!" These were their real last words and this was when they were on fire
It wasn't, that was them in the air. Their real last words was laughter and "shiii!"
😨😨😰
ีร่้้ี่าาเ้ิ่่ททมเดสกวกวย🛬❗💥✈️🛫
ีร่้้ี่าาเ้ิ่่ททมเดสกวกวย🛬❗💥✈️🛫
ีร่้้ี่าาเ้ิ่่ททมเดสกวกวย🛬❗💥✈️🛫
ีร่้้ี่าาเ้ิ่่ททมเดสกวกวย🛬❗💥✈️🛫
The guy in the atc saw the video:i remembered this...
That recreation is perfect big like/sub
Big thanks!
love the song 🎵 ❤️
What is the song name
@@Buskid57Young Girl A siinamota
@@Rice_AioonAviation oh
Yooo girl A hits so hard with this vid
"RIDE EM COWBOY!" famouse last words R.I.P😢😢
Btw wheres my package???????? I need it to my house. Edit:i liked my own comment :D
U have 1 like
No he has 8 likes
And now he has 12 likes
Now 16
IDK,mine was gone too.(My package)
This is the best one ive seen yet from all the other tfs recreations wow awesome dude!
ะิั่รานาคะพ_กถ้ีทนสนสคัถพภเัืรมยวน่ัเพกะืามนวยศรีะก/🛬🛫✈️💥❗
This is one of the best recreation from that game
Yes
How do i screen record?
Thanks for the support.
Yea
@Alfie8-United-kingdom bro i already know
bro I count the amount of pixels in that real life crash clip
What are you expect for the CCTV footage?💀💀💀💀💀
Bro it's in the 2003
@@Magmaboiz no its in 1997
@@BarneyCombine1997 was fedex 14
@@BarneyCombineI meant 2009 was fedex 80
now thats what i call op graphics
finally someone who can actually perfectly recreate it
I understood how hard to find one.
bro that isnt the perfect reacreate it needed to break the left landing gear
@@KRAVECRAVER1270 ..AND YOU AREN'T PERFECT.
You can't "easily"break the gear in TFS,it need to be fast,And if I was too fast and broke the landing gears,I can't do the bounce,And if I hiit the ground at that speed it will be ruin.
So sh-t the f-ck up.
I'm tried of every sh!t comments.
Do it then,If you think you are good.
@@Thanyaprat20773Exactly
@@Thanyaprat20773 noice
Best recreation good job mate
We have the same Turbolines💀
OAW Tarafından ✈️R:P
RIDE EM COWBOW
Famous last words
Song: Young girl a
edit OMG how do i get 2 reply
Edit again making story
FedEx Express Flight 80 was a scheduled cargo flight from Guangzhou Baiyun International Airport in the People's Republic of China, to Narita International Airport in Narita, Chiba Prefecture (near Tokyo), Japan. On March 23, 2009, the McDonnell Douglas MD-11F (N526FE)[1] operating the flight crashed at 6:48 am JST (21:48 UTC, March 22), while attempting a landing on Runway 34L in gusty wind conditions. The aircraft became destabilized at flare and touchdown resulting in an unrecovered "bounced" landing with structural failure of the landing gear and airframe, and came to rest off the runway, inverted, and burning fiercely.[2][3] The captain and first officer, the jet's only occupants, were both killed.[4]
FedEx Express Flight 80
The wreckage of FedEx 80
Accident
Date
March 23, 2009
Summary
Crashed on landing due to bounced landing caused by fatigue
Site
Runway 34L on Narita International Airport, Narita, Chiba Prefecture, Japan
35°45′35″N 140°22′40″E
Aircraft
Aircraft type
McDonnell Douglas MD-11F
Operator
FedEx Express
IATA flight No.
FX80
ICAO flight No.
FDX80
Call sign
FEDEX 80
Registration
N526FE
Flight origin
Guangzhou Baiyun International Airport, People's Republic of China
Destination
Narita International Airport, Japan
Occupants
2
Passengers
0
Crew
2
Fatalities
2
Survivors
0
Accident
edit
After making an approximately 1,800-mile (1,600 nmi; 2,900 km) overnight flight from Guangzhou, China, the air crew made an early morning approach to Narita Airport outside Tokyo.[5] Other traffic landing just ahead of the accident aircraft reported "wind shear" at an altitude of under 600 meters (2,000 ft)," and this information was relayed to the FedEx aircrew.[3] Surface winds at the time of the accident were reported from 320° at 26 knots (30 mph; 13 m/s; 48 km/h) gusting to 40 knots (46 mph; 21 m/s; 74 km/h).[6] After making a hard landing on runway 34L, the plane bounced three times, coming back down on its nose gear first (a condition called "porpoising") resulting in the loss of directional and altitudinal control. The left wing struck the ground as the gear failed, causing the aircraft to veer to the left, burst into flames and invert as the airframe broke up, and came to rest upside down in the grass to the left of the runway.[2][3][7] It took firefighters about two hours to extinguish the blaze, which completely destroyed the aircraft and its contents.[7]
Fatalities
edit
The only people on board the aircraft were the Captain, Kevin Kyle Mosley, 54, of Hillsboro, Oregon, and First Officer Anthony Stephen Pino, 49, of San Antonio, Texas.[4] Both pilots were removed to the Japanese Red Cross Narita Hospital (成田赤十字病院 Narita Seki Jūji Byōin) where they were pronounced dead. Captain Mosley, a former United States Marine Corps (1977-1983) fighter pilot, had been with FedEx Express since July 1, 1996 and had accumulated more than 12,800 total career flight hours, including 3,648 hours on the MD-11.[8] First Officer Pino, a former C-5 Galaxy pilot in the United States Air Force (1981-2004), joined FedEx Express in 2006 and had accumulated more than 6,300 total career flight hours, 879 of them on the MD-11.[4] Nobody on the ground was injured.
Runway closure
edit
Runway 16R/34L (length 13,125 feet (4,000 m)) was closed for many hours after the accident (with passenger flight cancellations or delays), leaving the shorter 16L/34R as the only available active runway.[9][10] As a result, many flights operated by larger aircraft had to be canceled or diverted to other airports such as nearby Haneda Airport, as 16L/34R is too short (length 7,150 feet (2,180 m)) for some types to operate safely, and some large aircraft types such as Boeing 777-300ER and Airbus A340-600 are restricted from using taxiway "B" (Bravo) which services that runway because of inadequate horizontal clearances.[11]
Aircraft history
edit
The aircraft involved in the accident, photographed two days before the accident at the same airport.
The aircraft involved when still in service with Delta Air Lines.
The aircraft was built in 1994[12] as an MD-11 passenger airliner. It was acquired temporarily by NASA to use as the test bed for their Propulsion-Controlled Aircraft system (PCA) in 1995.[13][14] Later it was owned and operated by Delta Air Lines from 1996 to 2004 under the FAA registration N813DE in such configuration.[15] The trijet was sold to FedEx in October 2004 when Delta retired its MD-11 fleet in favor of switching to more-efficient twin-engine Boeing 767s and Boeing 777s on its long-haul routes. Following its acquisition by FedEx, the plane was stored at Phoenix Goodyear Airport in Goodyear, Arizona[16] pending its conversion there to an MD-11F by Dimension Aviation, Inc.[permanent dead link], Boeing's Douglas Products Division airframe conversion contractor located at that field. The aircraft entered service with FedEx in its all-cargo configuration in late 2006 as N526FE. It was powered by three Pratt & Whitney PW4462 engines.[17]
Cause
edit
Learn more
This section needs additional citations for verification. (March 2016)
The Japan Transport Safety Board (JTSB)[18] dispatched six investigators to the airport.[19] The United States' National Transportation Safety Board (NTSB) sent a team to Japan to assist with the investigation.[10][20][21] The crash was FedEx's second fatal accident involving a jet aircraft, following the loss of a FedEx owned B747-249F that crashed February 18, 1989, near Kuala Lumpur, while still painted in the Flying Tigers livery after the acquisition of the Flying Tigers Line by FedEx in December 1988. This was the first fatal accident at Narita Airport.[1][10]
The accident was attributed by the JTSB to a series of "porpoising oscillations" that developed during touchdown,[22]: 97 following a high sink rate during the final approach. The first officer executed a late flare, in which sink rate was not suppressed until the plane was nearly on the runway, but which also would minimize "float" that might carry the plane further down the runway and reduce its safe stopping distance, or carry it off the centerline in the existing crosswinds. This high touchdown sink rate, coupled with large nose-up inputs, caused the first bounce. A large nose-down input was applied, causing a touchdown on the nose gear. This deviates from approved procedures for the MD-11 during a bounce, which specifies the pilot is to hold a pitch angle of 7.5 deg and use thrust to adjust the descent rate. The plane bounced off this second touchdown, pitching upward. The large control inputs by the first officer resulted in a hard touchdown on the main landing gear. This final touchdown was hard enough (1,200 ft/min (370 m/min)) to cause the left wing to fail as the left main landing gear transferred force up into the wing, exceeding its design limit. The JTSB report suggested the fire might have been averted if the landing gear fuse pin had failed as designed, but that much of the touchdown force was horizontal to the pin rather than vertical, keeping it intact. The report also cited the crew's use of autothrottle during landing despite gusty wind conditions.[citation needed]
As a result of this accident the Japan Transport Safety Board published its final report on April 26, 2013, in which it made a number of new safety recommendations including that "in order to reduce the occurrence of MD-11 series airplanes' severe hard landing and bounce in which an overload is transferred to the MLGs and their supporting structure, the Boeing Company should improve the controllability and maneuver characteristics by improving the LSAS (Longitudinal Stability Augmentation System) functions, reducing the AGS (Auto Ground Spoilers) deployment delay time and other possible means. Possible improvement on LSAS functions may include: a function to limit large nose-down elevator input during touchdown phase, which is a common phenomenon in severe hard landing cases accompanied by structural destruction for MD-11; and a function to assist bounce recovery and go-around in case of bounce. In order to help pilots to conduct recovery operation from large bounces and judge the necessity of go-around, studies should be made to install a visual display and an aural warning system which show gear touchdown status on MD-11 series airplanes."[22]: 97
The investigation into the two pilots' performance during flight 80 found that both exhibited signs of lack of sleep and fatigue, and the first officer was heard on the cockpit voice recorder talking about how he had not slept very much prior to operating the flight.[22]: 14 A look at both pilots' activity in the days leading up to the flight found that, based on accounts from hotel staff, credit card transactions, and other signs of activity, neither pilot could have had more than four hours of consecutive sleep in the twenty-four hours leading up to the crash.[citation needed]
Additionally, the pilot flying, First Officer Anthony Pino, usually served as a relief pilot, taking control in the middle of long-haul flights. He therefore had little experience in landing the MD-11, and performed landings very infrequently.[citation needed]
*Young girl A
/e pin
You should’ve said “its more than just a tfs plane crash”
Best recreation I’ve ever seen
The new Tfs update with fire would make it look way more realistic. You should try it! :)
Also, an Aeroflot flight crashed like so
#FedEX
Sorry to ask, but which app do you use to edit and record so well?
Nice question.
since "Capcut" updated and changed file type that NOT included in my phone
So I used "Vidma" and "Vidma Recorder" instead.
This happened to me when i brake my left wing
R.I.P to the 2 that died in the crash
@inovember4187no it was only the Pilot and Copilot cuz it was a package plane
Finally someone who dont roll to the right
Bro it's like in real life😮😮😮😮
Finally a video that does not have TFS plane fedex clash spiting in parts
The Famous Last Words Of the Flight 80 "Ride em cowboy"
Bro is trying to get fam
It was actually FUUUCKKKKKKK
You made the Night best FedEx 80 recreation in this game
Respect to the pilots for trying their best🫡
I love❤ basic livery in RL-72
😮😢
Same
Fed ex 80 last word ride em cowboy
nah it littreally was "shiii-hahahaha"
Ye in reality @@Yusuf-9
@@Yusuf-9 then big bang and metal noises
Bagi yang belon tau itu pilotnya capt kevin kyle. Mosley dan telah mekumpulkan total jam terbang 8.132 umurnya 54 dan fo anthony stephen pino telah mekumpulkan jam terbang 5.248 umurnya 49 saat kecelakaan saat 23 maret tahun 2009 dari guanzohou ke tokyo oo iya itu pesawat kargo pesawat saat jam 1 ini terbang normal selai terbang nya kira kira 3jam 26 menit dan cru dari fedex ini mulai berkomukasih sama menara control petugas control pun angin di runewe lalu roda pun di turun kan namun teryata pesawat itu megalami turbo lenci 2 kali tanpanya ada peringatan ketika roda pesawat pertama kalinya menyentuh daratan runewe pesawat ini langsung meluncur dan bagian belakang pesawat ini terbakar dan pesawat bener bener tidak stabil pesawat kemudian terbalik hingga sayap sebelah kirinya patah pesawatnya terbakar dan terus terseret 9 meter petugas e tisi yang melihat kecelakaan langsung menyalakan alamem lalu pemadam kebakaran langsung evokuasi dan 2 pilotnya wafat selesai 😢😢😢
😢😮😅😢
Game name: torboprop flight simulator
Turbo*
@AZTHENORMAL bro check the game name dum dum😭💀
its Turboprop Flight Simulator
@AZTHENORMALhe is right
@@L3tonkWhat do you mean? It’s Turboprop not Torboprop
The best one I’ve ever seen
The last words were
YEEHAW RIDE EM COWBOY
but the
SHIT SHIT SHIT
want the last words cause as you can see when the plane was upside down the pilot was still talking last words but he was supposed to be dead when the plane was upside down
The person after this: Screw it it just crash
Me: You don't know the pilots are trying their best to survive?
OMG thats REAL!!
Maybe fedex 14 cuz nighttime?
I’m taking about the tfs game
@@southjetairno because fedex 14 didn't bounce
@@TheGuy_WhoLovesCatmonnope fedex 14 bounced once.
FedEx 80 crashed around evening in Japan
(if I wasn't wrong)
@@Thanyaprat20773it crashed in the morning at japan
Ride em cowboy rip
Rest in peace to the pilots🥲
😮😮😮😮😮😮😮80
WHAT REAL LIFE FOOTAGE 😮😢
i love FedEx 80 and 14
The aircraft became destabilized at flare and touchdown resulting in an unrecovered "bounced" landing with structural failure of the landing gear and airframe, and came to rest off the runway, inverted, and burning fiercely. The captain and first officer, the jet's only occupants, were both killed.
CVR:
GPWS: 1000,500
Cap:I told you what to do
Cap:clear to land 24L
Cap:stable
*Firsts touch down*
Cap:shiiiiiiii
*Second touch down*
Cap:shiiiiiii hehehehe
GPWS:30,20,10
*Third touch down*
*Crash*
END
😢
☠️
Thats the same aircraft livery i have rn in that game
Perfect
Context: everytime when a plane flips over and the other wing strikes the runway, it gets zoomies
Context:Every times I checked my comments
It's always hurt.
(Nothing to expect this comment there always be a HATER who's ruining other feeling.
I'm serious.)
Perfec👌
R.I.P FedEx😢😔😔
I love the song 😊
Oh it's "Young girl A" (Japanese song)
@jessiemyrgalicia2607oh wow,You're plane lover,Don't you?
THIS SONG IS ABOUT OF SUICIDE
STOP 😭
@@doorsportugueseActually, The one of the singer of this song really did s!icided R.I.P
"RIDE EM COWBOY"!
famous last words 😢😢
I subscribed. Can you please recreate Asiana Airlines Flight 214?
❤ i dare you to make FedEx 14 for 1 beunce ❤
Yeehaw ride em cowboys
I love the music
The is the best now i see
They said my oil was cancelled 😭
Fact:in game,collapased right wing too
Rip 🪦 fedex flight 80 and 14
good butter bro
😮😮😮. Me gusta mucho
🎉
Its Perfection good 100/10
wait that is similar to my favorite game😮 chicken gun😮😮😮😮
thats not chicken gun blud
Good recreation
Thank you
qesawarmatl😭😭😭😭😭😭😭
Flight FedEx 80 actually . Because the Pilot were having fun and there was a slight wind disturbance it Caused the plane to ruleover
How did the airplane not go into pices thats like inposselbol like how and i loved this vid ❤❤❤
Game graphics
The game is fit for mobile if you have high graphics it'll be unplayable you need a high end phone to play this but most people might have old phones so the game dosent need good crash it'll just break into pieces that's why there's no fire
LOVE😢😮
Rip FedEx flight 14 we will miss you 😢
Use eagle air its purple like fedex 80
-wow-
Windows🥺😔
FEDAXMFLIGHT 80
Voice Lines:
GWS: 1000
GWS: 500
Pilot: Ready to land
Pilot: (Fixing something)
Pilot: Hahahahaha
Pilot: Hehehahahahahahaha
Ride’em cowboy 🤠
-the pilot
Explanation: there was a fedex 80 heading to Miami to Florida with no passengers suddenly the plane bounce 4 time then left wing was crushed
Last words. Fedex 14: hahahaha
Last words fedex 80:ride em cowboy
The crash you made was flight 80 and the real footage you show was flight 14
Wait,For real?
@@Thanyaprat20773 yep, fedex 14 footage is the real, the TFS crash is fedex 80. there are 2 (or 3 i think) FedExs crashes
GO UP
Game VS real
FedEx Flight 80 real life
👇
Wdym
that kinda looks like fedex flight 80 at start but then fedex flight 14 when he crashed
I swear to god this crash is everywhere on my fyp and its annoying
TH-camr favoritoooooooooooooooooooooo
Bro you almost do butter landing💀💀
I wish you were right but it is a real crash
Smoother landing then i can do and also rip
the airplane call ATR -72
You're right again
abc you love me
FedEx 14: brother i crashed in night
Now what that's a real crash
Here is the cvr: GPS: 500 plot: clear to co pilot: land 34L steble GPS: 30 20 10 pilot: shiiiii heheheaha bonce X3 *sound of crashing* rip to the pilot rip and co pilot):
Hehehehhihihihhahaha
-Fedex 80
FEDEX 80/FEDEX 14
🎉❤happy new year❤🎉
*pis I need a like*
Ppl who don’t know :😐
Ppl who know:😭😭😭😢🥺😭
💔😭😔😔😔😔😔😭😔💔😥😢😩😣😭
I like "Fed ex"
😢😮🥹😭🤦
Why is everyone milking FedEx 80’s crash on TFS 💀
Why does everyone ALWAYS got a 'problem" with it?😑