Loading video...

Video Failed to Load

Go Home

Something you don't see every day: a Lufthansa Boeing 747-8 (D-ABYP), operating flight LH402 from Frankfurt to Newark, experienced a strong burnt rubber smell about 20 minutes after takeoff. The odor resulted in an overweight landing, which caused overheated brakes. 📹: rywe(IG)

117,285 views • 1 month ago •via X (Twitter)

0 Comments

No comments available

Comments from the original post will appear here

Related Videos

Here's the full surveillance video showing moments before the Lufthansa Boeing 787-9 (D-ABPQ) nose gear collapsed at Frankfurt. If you watch closely, the nose landing gear doors open first, indicating what appears to be the start of a normal landing gear retraction sequence. According to reports, the Dreamliner had logged a maintenance request the previous day involving a landing gear door error message. On the Boeing 787, maintenance personnel can place the aircraft into a special maintenance mode (on the overhead panel, turn switch to "enable"). Boeing manuals emphasize that if maintenance mode is enabled, hydraulics are powered, and the gear lever is selected UP, the landing gear can retract regardless of weight-on-wheels protection. To prevent this, there's an override button where the gear handle lockout can be bypassed to move the gear handle even if it is locked out. The only way this can happen is by intentionally bypassing the normal safety lockouts used during maintenance procedures. Outside of maintenance or certain emergency procedures, the aircraft's weight-on-wheels system prevents gear retraction on the ground. Lufthansa says the aircraft has since been recovered. Fuel was removed, the jet was lifted, the nose gear was re-extended, and the aircraft was successfully towed under its own weight to a maintenance hangar. Germany's Federal Bureau of Aircraft Accident Investigation has completed evidence collection from the aircraft and is now gathering witness statements. An interim report is expected within approximately 8 weeks. 📹: airlinersde via YouTube, link on first comment here.

Turbine Traveller

542,172 views • 1 month ago

Breaking down what happened on China Airlines flight CI063 (Taipei to Vienna) on January 14, 2026... During takeoff from Taoyuan Airport, a tire tread from the main landing gear separated... a known occurrence with aircraft tires under high stress. The debris was flung upward and impacted the right wing, causing visible damage to the flaps and spoilers (no penetration to fuel tanks or critical structures). The passenger seated a Lufthansa aviation engineer, heard unusual sounds shortly after takeoff (around the time reaching Hong Kong airspace) and alerted the cabin crew. Initially told it might be normal, he persisted. When another pax overheard, he turned around, learned what was going on, and lent him his phone so he could show the crew takeoff video clearly showing the fresh damage. The assessment process took considerable time.. the crew consulted with the flight deck, maintenance teams on the ground, and dispatch while the engineer received periodic updates. With no critical warnings in the cockpit but visible structural damage confirmed, the captain elected to dump fuel and return to Taipei for safety. Aircraft landed without incident about two hours after departure. All passengers and crew were safe, and everyone was re-accommodated on later flights. Ground inspections later verified tire tread separation as the cause. The aircraft (B-18007, an A350-900) was removed from service for repairs, and Taiwan’s Civil Aeronautics Administration is investigating. The cautious decision to return was absolutely the right call, and the quick actions of an alert passenger plus thorough crew procedures prevented any risk from escalating. Aviation safety is layered for a reason. how much should passenger observations factor into in-flight decisions? Ever spoken up about something you noticed on a plane? Curious to hear experiences. ✈️ (Video from Pax seat attached... )

Fahad Naim

244,576 views • 6 months ago

Last night I asked Claude Code to build me a simple script: pull on-chain data from Polymarket and sort wallets by win rate Nothing ambitious. Just wanted to see who is actually making money on 15-minute BTC markets The terminal finished in about 20 minutes. Hundreds of addresses, columns of numbers, nothing interesting And then 1 wallet caught my eye 200+ trades per day, consistent profit every week, almost surgical timing precision. I reread the line 3 times. A real person does not trade like this I fed the address back into Claude Code and asked it to break down the pattern. Half an hour later I had a full strategy reconstruction on my screen The bot (and it is definitely a bot) pings Binance and Bybit every 100ms monitoring volatility compression on BTC. When it drops below 0.08% it enters Up and Down contracts simultaneously at 25 to 35 cents each. A pure straddle. 1 side burns, the other flies to a dollar. At a 30-cent entry that is 3 to 4x per position And so it goes in circles. Dozens of times a day I sat there staring at it for about 10 minutes $13K to $25K in daily profit from a single wallet. Not a trader with intuition, not an insider with information. An algorithm that found a hole in market mechanics and methodically milks it You can check the trade history yourself: After that I went looking for whether anyone else is tracking this wallet. Turns out yes. Found a Telegram bot that tracks wallets like this and copies their trades automatically I connected it to the same address just to see if the entries would match what my terminal was showing. Matched perfectly Still testing on minimum amounts for now: But the fact that you can stand next to an algorithm like this in real time is something that simply did not exist a year ago

Blaze

487,797 views • 4 months ago

💥 The Chinese authorities have known for 4 years that a pilot of a China Eastern Airlines jet — flight MU5735 — deliberately crashed the aircraft, killing all 132 aboard, according to data from the US. The data, released by the 🇺🇸 National Transportation Safety Board (NTSB), confirms earlier leaked US accounts that Flight 5735, a Boeing 737, was intentionally crashed into mountains in Guangxi in Mar 2022. The NTSB readings from the flight recorders show two pilots wrestling over the controls after both engines were shut down by hand, the automatic pilot was switched off and the jet was pushed into a nosedive as it cruised between Kunming and Guangzhou. In the face of public anger, Beijing has failed to publish a report. Last July the Chinese Civil Aviation Administration responded to an inquiry with a warning that “disclosure [about the crash] may, if released, endanger national security and social stability”. Beijing is under pressure from international aviation organizations to come clean over the disaster, which appears to have followed a similar pattern to suspected murder-suicide acts by airline pilots that have killed hundreds since 2014. The NTSB was asked to decode the flight recorders of Flight 5735 and transmitted its readings to China two weeks after their recovery in 2022. The US agency released extracts from its findings on Thursday in response to a Chinese citizen’s freedom of information request. “It was found that while cruising at 29,000ft, the fuel switches on both engines moved from the run position to the cut-off position,” the NTSB said. “Engine speeds decreased after the fuel switch movement.” Graphs of control inputs and the aircraft’s movement showed a pilot’s yoke pushing the aircraft into a steep dive and efforts by the other pilot to halt the dive. The two pilots were turning their yokes in opposite directions, commanding left or right rolls from the ailerons on the edges of the wings. The report said that a power failure had halted the data recorder after 90 seconds but the battery-powered crew voice recorder had continued. The agency did not reveal the contents, which it transmitted to Beijing at the time and said it had not stored a copy. Video from the ground showed the Boeing plunging vertically. The crew made no radio calls and no emergency radar code was transmitted. Previous Chinese reports have said that all systems appeared to have been functioning normally. Two months after the crash, a US investigator said “the plane did what it was told to do by someone in the cockpit”. China removed all references to that report, including screenshots, from social media. Three pilots were on the flight deck. Captain Yang Hongda, Zhang Zhengping, the first officer, and Ni Gongtao, a second officer in training. Speculation in China has centred on Zhang, one of the airline’s most experienced pilots, who had recently been demoted from his captain’s rank.

Byron Wan

348,300 views • 3 months ago

This Chinese developer launched Llama 70B locally on a MacBook on a plane and for a full 11 hours without internet ran client projects. He was sitting by the window on a transatlantic flight with a MacBook Pro M4 with 64 GB of memory. WiFi on board cost $25 for the flight. He declined. No cloud API, no connection to Anthropic or OpenAI servers, no internet at all. Just a local Llama 3.3 70B on bf16 and his own orchestrator script. The model runs through llama.cpp. Generation speed, 71 tokens per second. Context around 60,000 tokens. Memory usage, 48.6 GiB out of 64. Battery at takeoff, 3 hours 21 minutes. And he gave the orchestrator this system prompt before takeoff: "You are an offline orchestrator running on a single MacBook. There is no network. The only resources you have are local files in /Users/dev/work, the Llama 70B inference server at localhost:8080, and a battery budget of 3 hours 21 minutes. Process the queue at /Users/dev/work/queue.jsonl (one client task per line). For each task: draft → run local evals → save artefact to /Users/dev/work/done/. Save context checkpoints every 12 tasks so you can resume after a battery swap. Stop only on empty queue or when battery drops below 5%." So the system knows exactly what resources it is running on. It knows it has no connection to the outside world for the next 11 hours. It knows it has finite memory and a finite battery. It knows the human will not intervene until the plane lands. The system runs in 1 loop. Takes a task from the queue, runs it through inference, saves the artifact, writes a checkpoint. Task after task, just like that. And only when the battery drops below 5% does the orchestrator automatically pause, waits for the laptop to switch to the backup power bank, and continues from the last checkpoint. Here is what the system actually writes in his log during the flight: "saved context checkpoint 8 of 12 (pos_min = 488, pos_max = 50118, size = 62.813 MiB)" "restored context checkpoint (pos_min = 488, pos_max = 50118)" "prompt processing progress: n_tokens = 50 / 60 818" "task 37016 done | tps = 71 s tokens text → /Users/dev/work/done/proposal_westside.md" Outside the window, clouds, blue sky, and no WiFi. On the tray, 1 MacBook, an open terminal on 2 screens, and an inference server on localhost. From what I have observed, this is the cleanest offline AI workflow I have seen in the past year: 11 hours of flight, $0 for WiFi, and the entire client queue closed before landing.

Blaze

1,840,585 views • 3 months ago

100-TONNE TAKEOFF WEIGHT ERROR CAUSED B777 TAIL STRIKE AT MILAN On 9 July 2024, LATAM Boeing 777-300ER PT-MUG struck its tail during takeoff from Milan Malpensa after departing with performance data based on a 100-tonne weight error. Investigators found the crew used 228.8 tonnes instead of the correct 328.4 tonnes when calculating takeoff performance for São Paulo. The incorrect weight was verbally confirmed and entered into both pilots’ electronic flight bags. Since both devices used the same wrong figure, cross-checks matched and masked the error. No comparison was made with the loadsheet or FMC data. The consequences were immediate: • Reduced thrust setting • Invalid performance solution (“V SPEEDS UNAVAILABLE”) • Rotation and V-speeds far below safe values Correct speeds should have been approximately: V1 ≈ 172 knots VR ≈ 181 knots Instead, rotation began around the mid-140 knot range. The aircraft pitched to 8.3° nose-up within seconds. Tail-strike protection activated, but the tail contacted the runway at about 160 knots. By then the aircraft had passed the (incorrectly calculated) V1, making a rejected takeoff impossible. A third pilot in the cockpit called for full TOGA thrust roughly 12 seconds after rotation began. The aircraft finally lifted off at 178 knots with only ~800 metres of runway remaining, crossing the opposite threshold at just 155 feet. The crew declared an urgency, dumped 72 tonnes of fuel and returned safely. All 398 occupants were unharmed. The event was later reclassified from serious incident to accident due to structural damage found during inspection.

Turbine Traveller

101,771 views • 5 months ago

On April 26th, 2026, the Japan Meteorological Agency's Himawari-8 satellite captured a full day of Earth. Every ten minutes, for twenty-four hours, it photographed a complete hemisphere of the planet. One hundred forty-four individual photographs. No editing for content. No compositing. No CGI. No green screen. No hologram. No drawings. These are photographs, assembled into video. Himawari-8 is a geostationary weather satellite operated by Japan. It orbits at roughly twenty-two thousand miles above the equator, remaining fixed over one spot on the planet, orbiting at the same rate Earth rotates. It was launched in 2014. It takes photographs of Earth in visible light and infrared. It does this every ten minutes, every single day, year after year. These images are available to the public. Meteorologists worldwide use them for weather forecasting. News organizations use them. Scientists use them. You can access them yourself right now. What you're seeing over that twenty-four hour period is the terminator line moving -- the day-night boundary shifting as the planet's rotation carries different regions into and out of sunlight, all viewed from a fixed point in space. It is not a composite. It is not a trick. The curvature you see is not distortion. It is not perspective compression. It is the actual shape of the Earth as photographed by an independent satellite operated by a nation with no interest in perpetuating a NASA conspiracy. This is what Earth looks like from space. This is the globe holding atmosphere in place with gravity as you witness weather patterns moving across its surface. This is reality. (No fisheye lens was harmed in the making of this video.)

Alex Boge

12,122 views • 3 months ago