MythBusters tackles "plane on a conveyor belt problem"


Recommended Posts

Alright, I don't agree with what they did in Mythbusters!. When they pull that curtain with the truck the other way, the plane is still going and moving, it's gaining forwardness, it has to pick up! but when the belt is going the same speed with the plane, it wont allow it to move so no air on the wings, this isn't possible, mythbusters did this wrong, what do you guys think.

The plane can move forward regardless of the ground below. See my post above.

Something just didn't seem right about it, because it seemed like once the gas was pushed for the plane, it moved forward, never really matching the speed of the conveyor belt. It seems like that they want to achieve the same speed of both directions and then see if the plane takes off. Maybe I'm looking at this wrong?

They should build a large conveyor belt that doesn't require dragging a large belt on the ground. Those guys can do it!

The question describes the belt moving at the same speed of the plane (but in the opposite direction) just so that, at first, you incorrectly picture the plane being still ('cancelling it out'). But even if the question said the belt moved twice as fast as the plane, which would, at first, make you (incorrectly) picture the plane moving backwards, in reality the plane would still move in exactly the same way as if the ground was still. The speed of the belt really is of no importance (apart from technical details like how fast the plane's wheels can spin before overheating). Essentially the question is asking: does a moving runway affect a plane's take off?

Episode just aired, plane took off no problem. What was sad was that the pilot appeared not to understand how his plane functioned and believed his plane would remain stationary.

It's surprising how many people don't know how planes work, but you'd think pilots would understand.

It's surprising how many people don't know how planes work, but you'd think pilots would understand.

The problem (For most people, at least) wasn't that they didn't know how planes work, but that they didn't know quite what exactly the question was asking in the first place.

I always assumed the conveyor belt was just a way of saying "the plane is being kept stationary, can it still take off?" and if you look at the vast majority of the arguments against the plane taking off, they all talk about air flow and such.

If the plane is moving forward, there will be air flow, if not, there wont (and it wont take off). The myth was testing if the conveyor would stop the plane moving forward, that's clear now, but a lot of us (myself included) thought the myth was testing if the plane could take off from a stationary position.

The end result? Most people weren't really WRONG, it was more a case of whoever came up with the question didn't explain it well enough.

The end result? Most people weren't really WRONG, it was more a case of whoever came up with the question didn't explain it well enough.

But I think the whole point of the question was to catch out the people who thought it would stay stationary.

It's an excellent question because to answer to 'no' you have to have some understanding of aerodynamics, e.g. that a plane needs air going over its wings to gain lift. This knowledge makes you feel a bit smug and sure of your answer. The twist is that you need even more knowledge, about how planes get their thrust, to answer it properly.

But I think the whole point of the question was to catch out the people who thought it would stay stationary.

It's an excellent question because to answer to 'no' you have to have some understanding of aerodynamics, e.g. that a plane needs air going over its wings to gain lift. This knowledge makes you feel a bit smug and sure of your answer. The twist is that you need even more knowledge, about how planes get their thrust, to answer it properly.

People on both sides of the argument were incredibly smug about their answer, plus you don't really need THAT much knowledge to know that a plane gathers thrust from it's engines.

I still say the question was poorly worded, it should have asked "will the plane be able to gather enough forward momentum to take off?" rather than just "will the plane fly?".

Something just didn't seem right about it, because it seemed like once the gas was pushed for the plane, it moved forward, never really matching the speed of the conveyor belt. It seems like that they want to achieve the same speed of both directions and then see if the plane takes off. Maybe I'm looking at this wrong?

They should build a large conveyor belt that doesn't require dragging a large belt on the ground. Those guys can do it!

During the show they said what they did...

They first had the plane take off without the belt. They recorded the speed the plane was going when it lifted off the ground.

Then they put the plane on the conveyor belt and moved the truck at the speed previously recorded and started the plane moving. And as everyone saw it took off with no problem still.

I don't understand what doesn't seem right? They explained that a plane is nothing like a car and the ground has absolutely nothing to do with how a plane moves.

I think the reason the pilot didn't think it would take-off is because he wasn't a real pilot. He was an ultralight pilot. Ultralight pilots don't have to go through all of those pesky years of flight training and theory, I don't even think you need a license.

I didn't see the episode, I don't live in the states, but I read about it. You would think with so much controversy, they wouldn't half-ass it like it sounds like they did. It sounds like the plane was traveling much faster then the trap. If anyone knows a link to the episode, please post!

People on both sides of the argument were incredibly smug about their answer, plus you don't really need THAT much knowledge to know that a plane gathers thrust from it's engines.

I still say the question was poorly worded, it should have asked "will the plane be able to gather enough forward momentum to take off?" rather than just "will the plane fly?".

I didn't mean people were smug in a derogatory sense. I was just trying to explain how the question works on a psychological level. To answer no you have to have knowledge, which makes you feel like you know how to answer the question (sompare with someone who knows nothing about how planes work: they might not know how to answer at all, or will give a yes or no answer but for entirely the wrong reasons). I also realise that knowing how a plane gets thrust isn't a terrible amount more knowledge, I just mean that to answer properly you have to go beyond the initial bit of knowledge most rested on.

I also agree the question can be reworded, but like I said, the phrasing of the original is completely intentional in catching some people out. It's called a trick question.

I always assumed the conveyor belt was just a way of saying "the plane is being kept stationary, can it still take off?" and if you look at the vast majority of the arguments against the plane taking off, they all talk about air flow and such.

...

The end result? Most people weren't really WRONG, it was more a case of whoever came up with the question didn't explain it well enough.

The entire point of this question was to root out the people who thought the plane would remain stationary. This exposes the people who think of a plane as a winged car.

I knew something like this would happen:

Not A Believer! says:

It's a lie! It's all a lie!

I cannot accept their findings as they did not follow a method that I approve of, one that will guarantee that I am right that it's dumb to believe that an airplane can take off from a conveyor belt. Their test was stupid and not done correctly, the airplane was MOVING and that is so obviously wrong that I'll stop watching their show , their "treadmill" should have been moving much faster than the plane.

No matter what they say or prove, I cannot be made to believe that an airplane can take off from a conveyor belt. Better luck next time Myth-"busters".

? by Not A Believer! on Jan 31, 2008 at 07:15 AM

kottke.org

:laugh::

The entire point of this question was to root out the people who thought the plane would remain stationary. This exposes the people who think of a plane as a winged car.

Except that it didn't, not in my case anyway. I'm fully aware that a plane works completely different than a car. As I said, I never took the conveyor into the equation because the question was "can the plane still fly?" and not "can the plane outrun the conveyor?" or something.

Except that it didn't, not in my case anyway. I'm fully aware that a plane works completely different than a car. As I said, I never took the conveyor into the equation because the question was "can the plane still fly?" and not "can the plane outrun the conveyor?" or something.

If you never took the conveyor into the equation then the answer to "can the plane still fly?" would be an easy yes.

No, that's what I mean. Like I said, I took the conveyor belt to be a way of saying "the plane is stationary on the ground". So the engines are at full force, but the plane isn't moving forward. That's how I (and many others) interpreted the question and in THAT scenario, the plane definitely would not take off.

Everything Mythbusters did was absolutely correct and I'm not disputing their findings or anything, I'm just saying that there seems to be two real interpretations to the question and depending on which one you took would decide what your answer was.

No, that's what I mean. Like I said, I took the conveyor belt to be a way of saying "the plane is stationary on the ground". So the engines are at full force, but the plane isn't moving forward. That's how I (and many others) interpreted the question and in THAT scenario, the plane definitely would not take off.

Yes, you got caught in that trap. That is the trap for the people who think of a plane as a winged car.

The people who understood that a plane was not a winged car knew that the plane would go forward.

Yes, they knew it would go forward, but that never even factored into it for me and many others. Read what I'm saying, I interpreted the conveyor to just be a way of keeping the plane stationary, nothing more. It may as well have said "an anti-gravity field is placed upon the plane to prevent it moving forward" for all I cared.

The question never stated the plane can't move, it asks if the plane could fly if the tread mill matches it's speed (and it doesn't say what speed, air speed, ground speed, what part of the plane, etc.)

interpreted the conveyor to just be a way of keeping the plane stationary

How could you interpret it that way and NOT be exactly the type of person this question was trying to catch out?

I've never seen someone try to make so many excuses about getting a trick question wrong. Deal with it! It's meant to be light hearted!

It may be easier for some people to visualise the physics if they imagine the plane having frictionless pads in place of wheels and sat upon slippery ice. The plane's contact with the ground has little influence on the thrust driving the plane forward.

Wheels do not anchor planes to conveyor belts...

No, I thought the question stated it would be stationary, there's a big difference.

I don't really see a difference. If you understand how a plane works then you would know that it would not be possible to stay stationary.

I initially made the same mistake (if you look at my first post in this thread) but I quickly caught on and accepted that I was wrong.

I don't really see a difference. If you understand how a plane works then you would know that it would not be possible to stay stationary.

I initially made the same mistake (if you look at my first post in this thread) but I quickly caught on and accepted that I was wrong.

What I'm saying is that I thought the question was saying "the plane is stationary, what happens?" and not "will the plane BE stationary?". I thought the focus of the question was on how flight works and not on how ground force affects planes.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • GnuCash 5.16 by Razvan Serea GnuCash is a personal and small business finance application, freely licensed under the GNU GPL and available for GNU/Linux, BSD, Solaris, Mac OS X and Microsoft Windows. It’s designed to be easy to use, yet powerful and flexible. GnuCash allows you to track your income and expenses, reconcile bank accounts, monitor stock portfolios and manage your small business finances. It is based on professional accounting principles to ensure balanced books and accurate reports. GnuCash can keep track of your personal finances in as much detail as you prefer. If you are just starting out, use GnuCash to keep track of your checkbook. You may then decide to track cash as well as credit card purchases to better determine where your money is being spent. When you start investing, you can use GnuCash to help monitor your portfolio. Buying a vehicle or a home? GnuCash will help you plan the investment and track loan payments. If your financial records span the globe, GnuCash provides all the multiple-currency support you need. Between 5.15 and 5.16, the following bugfixes were accomplished: Bug 421610 - RFE: Include logical dates for View->Filter by "date range"The Select Range section of the Date tab of the register's Filter By dialog box is changed to provide relative, specific date, or days ago options for the start and end of the filter range. The Show number of days item label is changed to Show from days ago to better reflect what it does. Bug 436105 - esc key not working as expected in register: Enable the escape key to cancel a field edit. Bug 797384 - Gnucash doesn't handle commodity prices with big numerator/denominator properly. Bug 798004 - Next gen UI for stock transactions Bug 799314 - Add "enter now" option in scheduled transaction editor. tab to allow users to select the scheduled transactions to be included in a “Since Last Run…” window. If there are no instances of a selected transaction triggered by today’s date, the next instance is triggered. Bug 799751 - autocomplete crash Bug 799759 - Users can't Enable entries via Checkboxes on Scheduled Transactions PageAllow the Enabled box in the list of scheduled transactions to be operated instead of having to open the transaction editor dialog and change the Enabled checkbox. Also added use of the Name column as the secondary column sort for all the other columns. Bug 799762 - Poor handling of cases where hidden/placeholder accounts are used in the account register Bug 799766 - Double line preference not respected in search register Bug 799767 - POST /accounts in bindings/python/example_scripts/rest-api is broken Bug 799777 - `xaccSplitSetParent`: reparenting a committed split silently drops its KVP slots (online_id, cap-gains links) Other changes & improvements: Numeric values may now be selected to copy in the Accounts page. Add new Finance::Quote source Finnhub.io: Free API key (personal/non-professional use) available at https://finnhub.io. Set FINNHUB_API_KEY environment variable to API key to use this source. As of June 2026, free tier API limit is 60 API calls/minute. The Investment Lots report has new optional columns for Computed Annual Growth Rate. Python Bindings: Improved translation of primary object (Account, Transaction, Split, etc.) so that they can be treated as normal Python objects. This is accomplished with SWIG magic so no existing code is obsoleted. Python Bindings: Better conversion of GLists to Python lists. Python Bindings: Destroy the QofSession in the Python Session dtor to prevent leaving the database locked. [engine] Add first-class online_id accessors for Split and Account and make them available to Python bindings, removing the unused Transaction online_id property. Improve C++ implementation of QofBook. Correct the Doxygen doc for qof_instance_get/set_kvp. [gnc-log-replay.cpp] fix incorrect guid dump Add some Boost library requirements needed by libgnucash-guile to CMakeLists.txt so that missing feature will fail at configure time. Use Compile-time Regular Expressions instead of std::regex in gnc-filepath-utils.cpp and instead of boost::regex in the CSV importer, with the CTRE v3.11.1 header added to borrowed [gnc-filepath-utils.cpp] null check char* arguments Add ChartJS licenses. Removed AEX from list of commodities. euronext.com is now using JS based anti-webscraping. [report-core] always offer options summary in reports. This is useful to debug reports. The Add options summary option is removed because it's no longer optional. Remove remaining obsolete IMContext from sheet Fix blurry text in HiDPI offscreen-rendered widgets Add port field to database connection dialog: The convention of appending the port number after the host isn't obvious. When editing a split in the register treat the account as being changed only if it isn't the one selected before editing instead of if the user performed an edit Return immediately from qof_book_destroy if hash_of_collections is null. If qof_book_destroy is called on a QofBook* freshly created with qof_book_new (usually because it was used to create a session that now must be destroyed) it would try to empty the non-existent hash tables, crashing. Clean up Flathub metadata to solve warnings at flatpak build time. Be consistent in naming GncPluginPage and GncPluginPageRegister HTML: Remove unimplemented function declarations. [gnc-html.cpp] remove unused buggy string conversion functions Convert libgnc-html to C++ Apply -Wall -Werr -Wmissing-prototypes to C++ compilation on Windows and fix the resulting errors. New and Updated Translations: Arabic, Croatian, Danish, Dutch, German, Finnish, Hungarian, Korean, Norwegian-Bokmal, Spanish Download: GnuCash 5.16 | 176.0 MB (Open Source) Links: GnuCash Home page | Other Operating Systems | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • Microsoft finally launches WSL Containers in public preview by David Uzondu Microsoft has announced that WSL containers, a feature that allows developers to run Linux containers natively inside Windows without the need for Docker Desktop, is now available in public preview several weeks after Microsoft previewed it at Build 2026. To use the new container feature, you first have to install the latest pre-release version of the Windows Subsystem for Linux by running a quick update command in your terminal: wsl --update --pre-release After installing, you'd get access to the new Linux container CLI (wslc.exe) and the programmable API. Microsoft said that the CLI has a "familiar format" that matches the toolsets developers already use every day. If you know standard Docker commands, your muscle memory will translate directly to wslc.exe, which even features a built-in alias called container.exe. You can quickly run a full Ubuntu KDE desktop container by exposing ports, or pass your graphics card straight into a machine learning environment to run PyTorch workloads. Passing the --gpus all flag inside the run command instantly links your hardware. Image via Microsoft As for the API, developers can now embed Linux container operations directly inside native Windows applications without exposing the command line to users. The team integrated the API directly into MSBuild and CMake, so developers can define container steps directly in project files. Apart from bringing the CLI and API into public preview, Microsoft also said that it's working on a new default file system called virtiofs to speed up file transfer rates between Windows and Linux. Microsoft also introduced an experimental networking mode named consomme, which resolves compatibility issues with corporate VPNs by routing Linux network traffic straight through Windows. One thing to note about WSL containers is that they don't run in your standard WSL distributions; instead, every application and CLI session spawns its own lightweight Hyper-V utility VM in the background. This basically reduces the chances of one app snooping on the container of another app.
    • Google reportedly limited Meta's Gemini access over limited AI compute by Karthik Mudaliar Google is reportedly limiting Meta's use of its Gemini AI models after Meta tried buying more computing capacity than even Google could supply. According to the Financial Times, Google told Meta in March that it could not provide the full Gemini capacity that Meta had requested. This shortfall even disrupted and delayed some of Meta's internal projects. Due to this, Meta even told its employees internally to use AI tokens more efficiently. Meta wasn't the only one to get hit by this sudden refusal by Google; even other customers were affected. But Meta was hit harder because of its unusually high demand for Google's models. The move from Google makes it evident that companies all over are in limited supply of both infrastructure and compute. Alphabet said in April that Google Cloud revenue grew 63% year-over-year to $20 billion in the first quarter, helped by enterprise AI infrastructure and AI solutions. In pursuit of more compute, Meta had earlier signed a multi-billion-dollar AWS agreement as well as a large AMD GPU deal for AI data centers. But the crunch would be short-lived as both Meta and Google have also ramped up infrastructure investments heavily. Meta said in November that it was committing more than $600 billion in the U.S. by 2028 for AI technology, infrastructure, and workforce expansion. In the first quarter of this year, Meta also raised its expected capital expenditure for 2026 to a range of $125 billion to $145 billion, citing higher component pricing and additional data center costs for future capacity. However, this doesn't make the company immune to the current dependence on outside suppliers. Meta has also spent many years promoting Llama as an open-weight alternative to closed models from Google, OpenAI, and Anthropic. But if the reported reliance on Google's Gemini models is severe enough for internal work to get impacted, then it looks like even frontier labs and Big Tech aren't fully self-sufficient. Source: Financial Times
    • I like to reminisce about the good old days, way back in autumn 2025 when building a gaming machine was fun and the drives were about $150 when you caught a deal. Yes duh, back in the day we had it gone. Then baby Skynet came along, hiding in AI datacenters demanding more processing power until it reached singularity. End of a not totally fictional story.
    • My experience in the past with older Windows 11 builds was not great on unsupported machines but I recently used Rufus to put the latest build on a older 5th Gen Core Thinkpad T that we upgraded with a SATA SSD and 8GB of RAM four years ago when hardware was reasonable and it seemed pretty fast and solid. Customer is very happy with the performance and will probably get four more years out of that venerable laptop that he loves so much. Another customer just retired his Dell Studio laptop from 2009 running Windows 10. It got an SSD over 10 years ago and did everything he needed it to for 17 years but he also retired last year and is happy doing everything on his iPad now.
  • Recent Achievements

    • Reacting Well
      NovaEdgeX earned a badge
      Reacting Well
    • Week One Done
      NovaEdgeX earned a badge
      Week One Done
    • One Year In
      BA the Curmudgeon earned a badge
      One Year In
    • Conversation Starter
      rosiecharles earned a badge
      Conversation Starter
    • First Post
      KMilenkoski1202 earned a badge
      First Post
  • Popular Contributors

    1. 1
      +primortal
      533
    2. 2
      +Edouard
      269
    3. 3
      PsYcHoKiLLa
      150
    4. 4
      Steven P.
      98
    5. 5
      macoman
      66
  • Tell a friend

    Love Neowin? Tell a friend!