coyotepup

Members
  • Content Count

    610
  • Joined

  • Last visited

Community Reputation

1 Neutral

About coyotepup

  • Rank
    Anarchist

Profile Information

  • Location
    Michigan

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. coyotepup

    Port Huron - Mackinac 2019

    Credit to the weather forecasters for nailing the direction of the breeze from Sunday afternoon to Monday afternoon. Huge demerits for being about 200% off on velocity. "Get a weather radio and find out how long this shit is going to last" says our skipper. OK. Answer: ¯\_(ツ)_/¯ According to weather radio, current observations claimed to be 12-14 knots. Hey, what does the instrument say? "Uh, 28." Weather radio is hereby fired from duties in predictive capacity. Fortunately, nothing broken and no injuries, although the same can't be said about every boat on the shore course.
  2. coyotepup

    “Knot” a cool pun: worst boat names ever

    Not a fan of writing "too" in place of "2." Rhumb Runner is the deadest of dead horses as well.
  3. coyotepup

    Tanker hits Destoyer, how is this possible?

    I suggest you inform the Navy that you have the answer to the questions they're asking, they'll be glad to know they can put down their pencils and issue a report to that effect. I can't imagine why neither them nor any of us have come to such an obvious conclusion based on the partial evidence we have in front of us.
  4. coyotepup

    Tanker hits Destoyer, how is this possible?

    Yeah, that's because the report was a report specifically on the damage control efforts, not the causes of collision.
  5. coyotepup

    Tanker hits Destoyer, how is this possible?

    Yes, I'm well aware, I read the whole report from top to bottom. The collision happened at 0130 local, this is perfectly well established, and the Crystal was at position 2 at 1630 UTC, which is 0130 local. Period. They changed course before the collision. Obviously. They didn't just slam into each other without some kind of course change first. The fact is that in every Navy collision not involving a submarine, and I was required to study basically all of them, course changes happen before the collision. Ships don't blunder blindly into each other, and as fun as it has been to wonder why a team of trained Navy officers and watchstanders with radar up the wazoo couldn't see a massive container ship, I think it's time to understand the truth here: they are absolutely guaranteed to have seen the Crystal, probably from a very long way away, and made a very large mistake in judgment as to what the Crystal was doing. Common threads in all collision case studies have been these: the ships involved definitely saw each other, and failed to recognize the other as a threat to collide until it was too late, at which point they made a large rudder change to fruitlessly try to avoid the inevitable. One way or the other, that's what will come out in the wash here. But the collision was still at point 2 on the Crystal's track.
  6. coyotepup

    Tanker hits Destoyer, how is this possible?

    The collision was at position 2, we know this because of the times listed. 1630 UTC is 0130 local. What's interesting is that the Fitz was steering 230.....making this very likely a head-on situation and not a crossing situation. Reciprocal of 230 is 050, very close to the 068 Crystal was steering. The next question is how do the ships go from a nearly head-on aspect to the collision aspect described. Perhaps the Crystal turned hard starboard (as its captain described) and the Fitz turned even harder to port at the same time. Perhaps the two ships interpreted the situation differently - one as a crossing and the other as a head-on. Different nav light aspects could cause that.
  7. coyotepup

    Tanker hits Destoyer, how is this possible?

    I would tend to dispute the conclusion, obviously, but even if 100% true, squawking AIS isn't going to change that. It might make it worse, if you adopt the idea of having a rotating fake name. "Who are we this week, again? The M/V Galactic Superstar?" "No, that was last week, now we're the SS Megalithic." I'm sure it would be a bullet in the nav brief, but still. And then, of course, the jig is completely up the moment the "Megalithic" responds on VHF (especially if accidentally as "Warship 5-4" which is how Navy ships refer to themselves on VHF) and it's obvious to the entire friggin' world that "Megalithic" is actually the big gray warship. How many merchant ships are going to confuse themselves with a Navy warship? And if they missed the "Navy warship" part of the call, then they'd have missed anything in that part of the call, whether it's a ship name or not. And in the end, what's the worst that happened in your scenario - a couple bridge watchstanders on uninvolved ships were inconvenienced and had to spend a couple minutes updating on their situational awareness? Horrors. And radar will pick up a contact a LONG way away. This is not something that happens within a mile or two. It happens within ten or twelve miles. Perfectly adequate time for a CPA to be calculated. The Navy is not going to hand potential adversaries a tool to track their ships and learn their traffic patterns. Yes, it can be done in other, more difficult ways. Why make it easier?
  8. coyotepup

    Tanker hits Destoyer, how is this possible?

    By the way, I think squawking AIS, even with random, rotating names, is not a good idea. No, the Navy is not deluding themselves into thinking not squawking AIS makes them super-secret. The Navy knows it's not sneaking around. But neither is it wise, to give possible enemies one extra tool in the toolbox. Might it be a small, incremental step in avoiding collisions? Sure, just as it's a small, incremental step toward giving somebody a way to blow up the ship. I don't think it's a good trade off. Even if you had a list of 25,000 random ship names (that would last about a year and a half, if every Navy ship had one and changed it weekly) any idiot could look against the international ship register, see that that name isn't on there, and conclude it's a Navy ship trying to hide itself. The only thing worse than running around going "I'M A NAVY SHIP" is pretending not to be one in blatantly transparent ways. The only real advantage I see is that it would give the merchant ship a name to call a Navy ship. Its radars should still pick it up as a surface contact and track a CPA. A halfway decent radio call in any case - whether or not you know the name of the contact - should give the ship you're hailing your range and bearing from them. "Navy warship, Navy warship, Navy, warship, this is ACX Crystal, 6,000 yards off your starboard bow." You don't need a name to make that call and now you've made yourself perfectly clear. No AIS required.
  9. coyotepup

    Tanker hits Destoyer, how is this possible?

    Just like every Marine is a rifleman, every sailor is a firefighter. But actually, these days, they make an announcement that "the ship is in a training environment" before setting off any alarms. I think this is so that guys don't drench some poor engineering chief waving a "class B fire" flag with AFFF and make an unholy, very possibly damage-causing, mess of the engine room in the process. Insufficient hustle was still met with an order to shape the hell up.
  10. coyotepup

    Tanker hits Destoyer, how is this possible?

    True, I recalled this being the case as I typed and changed my post from "never" to "mostly." Most DC drills we ever had involved fire, though. Flooding drills were usually given as the result of hitting a mine or someone shooting a missile. Alarms do go off when the ship's in a training environment, but I don't ever recall the situation being "we bumped into another ship and now there is flooding." Same situatio (flooding below the waterline), different cause (enemy action.)
  11. coyotepup

    Tanker hits Destoyer, how is this possible?

    That's really going to depend on the ship, to be honest. Probably depends on the personalities of the people on the bridge. I don't think the answer will be found in the broader Navy culture. I can tell you that the helm is going to obey the orders of the conn, whatever they are, and a reasonably experienced conn would probably turn the ship. A conn fresh out of school might not. (By the way, June is when a new wave of brand-new JOs show up to their ships in droves, and the conn is the first place they go. Just throwing that out there.) JOODs are all different too. But they wouldn't be guided by Navy culture, they'd be guided by ship culture and their own level of experience. When it comes to sounding the collision alarm, I have two theories I think are more plausible. 1, if they didn't know a collision was happening they wouldn't have sounded the alarm - and the location of the damage on the Fitz and on the Crystal suggest it's possible they really didn't ever see it. 2, they forgot, because sounding the collision alarm not only is exceedingly rare, it's also not often trained for. You're told it exists, and you're told when to sound it, and it's not like nobody knows about it, but mainly you train to avoid collisions, not for what to do in the event you have one.
  12. coyotepup

    Tanker hits Destoyer, how is this possible?

    The "emergency starboard turn" that was followed by a collision ten minutes later, and that somehow doesn't show up on the AIS track, per the captain's report that you take as gospel? Ironic that you are relying on a very questionable (at best - and at worst, full of lies) report, written by someone with a clear self-interest, which doesn't match the automated AIS track, as a way to bolster your argument in favor of automation.
  13. coyotepup

    Tanker hits Destoyer, how is this possible?

    Why all the extra-special love for automation? It didn't keep the ACX Crystal from hitting a big gray destroyer.
  14. coyotepup

    Tanker hits Destoyer, how is this possible?

    On the one hand, I wouldn't call it "more than enough" - you'd need the truth about what was being discussed, if the Crystal was ever a topic, etc. On the other hand, if the QMOW keeps his wits about him, as you'd hope, he ought to look at the clock when the ship goes BANG and calmly write "0130:00 - Collision with merchant vessel". He should also record if and when the collision alarm was sounded. When the investigators come on board, they'll make a beeline for that log.
  15. coyotepup

    Tanker hits Destoyer, how is this possible?

    IMO the Navy would rather have 1,000 years of totally baseless speculation than one officer in full uniform say anything even remotely false, even with the best of intentions and to the best of his or her knowledge. The press won't be tossing beach balls. And the NYT used a single anonymous sailor's quote as an "epitaph for the accident", splashing it everywhere and acting as though it might as well be the final word. Imagine how they'd treat a quote from an officer in whites with a stack of ribbons and a nametag. Official Navy gospel on the matter, is how - and then woe betide the Navy if that gospel changes.