HORNET BAY
FLIGHT LOG
← ALL ENTRIES
#CONTENT — 7 ENTRIES
SITECONTENT

TOP PILOTS — a MiG-kill leaderboard on the title screen

The Hornet Bay title screen with a new TOP PILOTS · MiG KILLS panel at top right, listing sample callsigns MAVERICK, GOOSE, ICEMAN and ROOKIE2 with their kill counts, beside the main menu

The title screen now has a leaderboard: TOP PILOTS, ranked by MiG-29 kills. Set a callsign in your pilot log, splash a MiG, and your name goes on the board.

Until now the front door only showed fleet-wide totals. That tells you the Bay is busy; it doesn't tell you who is winning the fight. The new panel sits top right on the title screen and lists the five pilots with the most MiG-29 kills, with the leader in gold.

How it works

The screenshot above uses sample callsigns; the live board fills in as pilots earn their places. If the leaderboard service is unreachable the panel shows the last board your browser saw, or hides itself rather than showing an error.

Try this: set your callsign from the pilot log, fly a sortie and take down a Fulcrum. New to the sim? Start with flight school; the fleet totals strip is explained in By the numbers.

— HB

The order of battle — everything that flies, sails and shoots in Hornet Bay

The Hornet Bay aircraft gallery: a grid of fifteen low-poly models on the floor, including the F/A-18 Hornet, F-14 Tomcat, F-16, Air Force One, MiG-29, several airliners, a cruise missile, a P-3 Orion, an SH-60 Seahawk, an AH-64 Apache and an E-2C Hawkeye

Hornet Bay has a lot of metal in it now. Before we start taking it apart one airframe, one squadron and one hull at a time, here is the whole roster: what flies, what sails, what shoots, and who you meet in the Bay. It also kicks off something new: an article every day for the next 90 days.

YOU FLY

THE HOME TEAM

THE OTHER SIDE

THE ARMOURY

EVERY DAY FOR 90 DAYS

From tomorrow the Flight Log runs a weekly rhythm, and every post lands at a different hour of the day:

Every model in this roster also lives in the 3D Print Bay: 37 of them. Keep the RSS feed handy so the daily posts find you. — HB

SITEUXCONTENT

Cards for every post, a banner that flies home, and a search box back in formation 4d13ee5

The flight log header — the Search Flight Log box riding the same row as the two nav buttons, with the tag squadrons rail at the right

Three site chores landed in one sweep — one visible alignment fix, one clickable banner, and a full dress uniform for every journal link you share:

  1. The search box is back in formation. Search Flight Log rides the same row as BACK TO THE COCKPIT and RETURN TO BASE — 59 pixels to 59 pixels, tops aligned — while the squadron-store links keep the row below to themselves. Phones stack the lot, search full-width.
  2. Every post now ships its cards. All 134 journal entries carry an optimised meta description (cut at a sentence where one fits, 155 characters budget), a complete Open Graph card — image with its true pixel dimensions read off the file, secure URL, type, alt text, locale, published time and one article:tag per squadron — and a complete Twitter card: summary_large_image, site and creator @hornetbay, a title trimmed to 70 characters, and alt text on the image. Drop a link anywhere and it arrives in dress uniform.
  3. The banner flies home. The laurel header on every one of the 212 pages is now a link back to the homepage, with a soft amber glow when you hover it. One template, one shared stylesheet, one sweep — every page born from here on carries it.
  4. Found and fixed in the sweep: four old headlines carried spliced markup from an ancient hash-stamp — one title duplicated mid-word, four wearing two hash badges. All repaired, and the rebuild now audits every page: descriptions under 160, Twitter titles under 70, no exceptions.
SITEUXCONTENT

Five squadrons: the tag rail files its paperwork 0b53c94

The flight log sidebar with five parent tag squadrons — THE GAME expanded to show its child tags with post counts

Thirty-five tags was a roster, not a filing system. The flight log’s sidebar now squadrons up — five parent categories with the child tags tucked into sub-menus — and a little menu housekeeping flew the same sortie:

  1. Five squadrons, every tag assigned. THE GAME (19 tags: FEATURE, CONTROLS, BUG FIX, SIM, the whole flying machine), MISSIONS & THE FLEET (7), THE SITE (5), SQUADRON STORES (2) and THE SQUADRON (2). Parents show their child count and open an accordion of chips — one squadron on the board at a time, each child carrying its post count.
  2. The rail still flies the same. Clicking a child filters exactly like before, the parent lights amber when one of its own is on the board, and a #tag= link auto-opens the right squadron — search and paging are untouched.
  3. Duplicate spellings merged. FIX and BUGFIX both become BUG FIX — 37 tags down to 35 and one spelling from here on. The old flat tag strip stays in the markup for the crawlers but no longer takes up the page.
  4. Same sortie, lighter menu. GALLERY has left the main menu — spectate view does its job now — and the ANALYTICS dashboard page is retired (the counters still tick quietly in the background). The social chips on the menu footer and every blog footer are bigger, bolder, and a lot easier to hit.

Meet the giants of the lane e881dce

CONTENTFEATURE MT Petro Pacific, the 360-metre supertanker, broadside on as the Hornet passes low abeam

The shipping lanes between the Bay and the Pacific have gone heavy. Four new hulls now work the lane in both directions — three deep-laden supertankers and a cruise liner — each one named and typed in the traffic system, each trailing a wake scaled to its length. Meet the new traffic, largest first:

  1. MT PETRO PACIFIC — 360 m overall, 54 m beam, 3.5 kt on the lane. The biggest hull in the bay; she barely answers her helm.
  2. MT GOLDEN CRUDE — 340 m, 50 m beam, 3.8 kt. Black hull, rust-brown deck, pump manifold amidships, accommodation castle right aft.
  3. MT ATLANTIC BULK — 320 m, 48 m beam, 4.0 kt. The sprinter of the tanker trio — which, granted, is not saying much.
  4. MS BAY MONARCH — 230 m, 30 m beam, 6.8 kt. The cruise liner and the fast mover of the lane: stacked white decks, window bands, and the line’s amber band on the funnel.

Seamanship notes: after dark all four show proper lights — white masthead, red to port, green to starboard — and every hull leaves a wake you can pick out from altitude. They share the water with the existing freighters, fishing boats and yachts, so the Golden Gate is properly busy now.

One word to the wise, pilots: file these names away. The mission desk has been asking an unusual number of questions about lane schedules of late — best to know a supertanker from a cruise liner before the tasking orders start mentioning hulls by name.

MT Golden Crude working up the lane, wake streaming astern, Hornet in the foreground MT Atlantic Bulk seen over the Hornet's tail, rust deck and white castle MS Bay Monarch, the white cruise liner, passing beneath the Hornet

Cockpit-off, spectate tweaks & the giants of the lane 1a0d222

FEATURECONTENT Chase view of a supertanker plying the Golden Gate shipping lane at dusk

View system overhaul: V now cycles cockpit → cockpit-off → chase → orbit → tower. Cockpit-off is the pilot’s-eye view with full symbology and no glass or panel in the way. Spectate (J) no longer shows your own jet or the cockpit furniture while you ride along — just a clean SPECTATE banner, and X drops you straight back into the cockpit. The F1–F10 throttle row has been retired from the flight manual (the bindings themselves are untouched), and the title screen now reads Carrier Ops Flight Simulator.

The shipping lanes are getting heavy: three supertankers — MT PETRO PACIFIC (360 m), MT GOLDEN CRUDE (340 m) and MT ATLANTIC BULK (320 m) — plus the cruise liner MS BAY MONARCH now ply the lane between the Bay and the Pacific. All four are named and typed in the traffic system, ready to be tasked in future missions.

Brand desk: the Squadron Laurel roundel has been re-shot — the complete Hornet now appears from the original emblem’s camera angle, whole airframe inside the ring. Files on the assets page.