Talk:Moruya Airport

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia

Untitled[edit]

I have reverted to my previous edit that was done by a known sockpuppet to a banned user. PLEASE do not add information unless you have a source.... for example you CANNOT operate a 747 into YMRY because it only has a 1500m runway, that is code C rated and only 30m wide. A B747 REQUIRES at least 2000m of runway at code D and 45m wide. The only SOURCED operator into YMRY is Regional Express using Saab340 type aircraft. I have left their routes on as they are accurate currently, QantasLink doesn't currently fly there.

MEBpilot (talk) 06:20, 8 January 2008 (UTC)[reply]

External links modified (February 2018)[edit]

Hello fellow Wikipedians,

I have just modified one external link on Moruya Airport. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:

When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.

This message was posted before February 2018. After February 2018, "External links modified" talk page sections are no longer generated or monitored by InternetArchiveBot. No special action is required regarding these talk page notices, other than regular verification using the archive tool instructions below. Editors have permission to delete these "External links modified" talk page sections if they want to de-clutter talk pages, but see the RfC before doing mass systematic removals. This message is updated dynamically through the template {{source check}} (last update: 18 January 2022).

  • If you have discovered URLs which were erroneously considered dead by the bot, you can report them with this tool.
  • If you found an error with any archives or the URLs themselves, you can fix them with this tool.

Cheers.—InternetArchiveBot (Report bug) 03:01, 6 February 2018 (UTC)[reply]