Colin Parkinson
Army.ca Myth
- Reaction score
- 12,010
- Points
- 1,160
Well that article hit all the correct talking points, climate change, environment, etc.
Just sounds like it's been heavily massaged by a PAO. But yes I am glad to see them operational.Training, crew, back to sea. A little bit for everyone. I'll take that article as a win. I found it interesting and informative.
Just sounds like it's been heavily massaged by a PAO. But yes I am glad to see them operational.
“It’s a daunting task, sailing that farup North. I’m not too sure how to prepare myself emotionally, psychologically, operationally for this,”
MARS: Comments?This bit sounded particularly insincere:
If taken seriously, somewhat disappointing and uninspiring coming from the ship's CO...
I assume it was just meant to play up the excitement for the "unknown".
It's completely honest and in my mind refreshing. It is daunting. And it is difficult. This isn't a walk in the park. You are really very very far away from help if something goes wrong in a badly charted land. It's a lot more risk then sailing pretty much anywhere else in the world for a CO to undertake.This bit sounded particularly insincere:
If taken seriously, somewhat disappointing and uninspiring coming from the ship's CO...
I assume it was just meant to play up the excitement for the "unknown".
Agreed, it reads like an insincere attempt to play up the risks.This bit sounded particularly insincere:
If taken seriously, somewhat disappointing and uninspiring coming from the ship's CO...
I assume it was just meant to play up the excitement for the "unknown".
Renewing the Canadian Coast Guard’s fleet ensures our personnel can continue carrying out critical work with modern and safe equipment, while creating good skilled jobs in our shipbuilding and marine industries across the country.
Today, Mike Kelloway, Parliamentary Secretary to the Minister of Fisheries, Oceans and the Canadian Coast Guard was joined by the Honourable Sean Fraser, Minister of Housing, Infrastructure and Communities to celebrate the steel cutting milestone on the first of the two future Arctic and Offshore Patrol Ships for the Canadian Coast Guard, marking the official start of construction of the vessel undertaken by Irving Shipbuilding Inc. from Halifax, Nova Scotia.
The Canadian Coast Guard’s new Arctic and Offshore Patrol Ships will operate as a primary platform to support fisheries enforcement missions on Canada’s east coast, including Northwest Atlantic Fisheries Organization patrols. They will also support search and rescue and icebreaking operations on the east coast, strengthening Canada’s presence in the low Arctic.
In addition to their primary missions, the Arctic and Offshore Patrol Ships will be able to support environmental response and aids to navigation, allowing greater flexibility and adaptability for the Canadian Coast Guard’s operations. Outfitted with science equipment and a medical facility onboard, these modern and versatile ships will be able to conduct scientific research and support humanitarian assistance missions.
The two ships are built under the National Shipbuilding Strategy’s large vessels construction pillar. Through the National Shipbuilding Strategy, the Government of Canada continues to make significant investments in modernizing the Canadian Coast Guard fleet while creating good skilled jobs in our shipbuilding and marine industries across the country.
The Canadian Coast Guard’s Arctic and Offshore Patrol Ships project will contribute to more than $125M annually to Canada’s GDP, and create or maintain close to 1,250 jobs annually in the Canadian shipbuilding industry over the 2022-2030 period.
The first Canadian Coast Guard Arctic and Offshore Patrol Ship is expected to be delivered in 2026. By 2027, the Canadian Coast Guard’s fleet is expected to include two new Arctic and Offshore Patrol Ships.
The Arctic and Offshore Patrol Ships will replace two of the Canadian Coast Guard’s existing five Offshore Patrol Vessels. The vessels are 103 metres long, 19 metres beam, with approximately 6,677 metric tons displacement.
Boaty McBoatFace?Strangely still no naming scheme announced for either.
TBH to me it’s either over the top drama, or poor leadership.It's completely honest and in my mind refreshing. It is daunting. And it is difficult. This isn't a walk in the park. You are really very very far away from help if something goes wrong in a badly charted land. It's a lot more risk then sailing pretty much anywhere else in the world for a CO to undertake.
Just getting fresh groceries is a massive chore. GPS doesn't work properly, there are no SATCOM's to call for help, you have to rely on HF for your beyond visual horizon coms. And the ships though proven still have much of the new car smell so have more risk.
It's completely reasonable for a new CO to have concerns, and voicing them to his crew is likely a sign of his leadership style.
To be honest I've been all over the Arctic and pretty far up north and its somewhere not to be screwed with and have a healthy respect. Things can go wrong quickly and rescue is not always possible or quick due to the isolation. You need to prepare and know what your going into. The good thing is plenty of RCN ships went there before them and we have a whole mechanism to lessons learned to answer those questions along with picking up the phone and talking to CO's who actually been there. I'm pretty sure that CO has asked the questions, and received the information they need to be successful and the RCN is not in the habit of sending a CO without being prepared. I been around long enough to keep doubts to myself and if I have them to gain the knowledge I need to dispel them.TBH to me it’s either over the top drama, or poor leadership.
Yes you can have concerns, but suggesting you don’t know how to prepare is beyond problematic.
Honestly if he doesn’t know how to prepare properly, he should be relieved.
ATL used to have a floating drydock in the Western Arctic. At some point it might be wise of us to have another one stationed up there, it would have to be mostly subsidized, but it would be a great assets in the long run.I've just started referring to them as 'Lesson's written down', which then become 'lessons forgotten'. Pretty much every after action report to the Med in the last decade has the exact same lessons learned and recommendations to CJOC, and with the timing of when they go in if you are lucky you just get it from the ship you are replacing two months before, instead of relying on the last one.
We really suck at lessons learned as an institution, and consistently find that major incidents had a lot of identical minor incidents or near misses before something major happened. They also don't get shared well between coasts, as there are local databases for TIs etc. I know a lot of people didn't like the old PELs (because they sucked at writing them so that they were useful) but lots of things like that we just stopped doing because someone thought it was inconvenient.
People get lost in the sauce a lot.So many other things become immediate and important. Trying to get the ship ready engineering wise for a deployment doesn't leave the dept heads (PO2 and up) much time to peruse the previous deployments lessons learned. Something that sea training always nails you on of course.
And you're trying to get your individual training sorted, your DAG done, ensure the dept does the same, find people to fill positions... list goes on. Lessons learned are great, but where's the time! I've only got so many hours in the day...
I think we need to differentiate experience (which we need as well) from lessons learned. Lessons learned as far as I understand it is learning from others experience.I will observe that when you post a crew off after a major deployment, it's a broken chain of lessons learned.
When I was on CHA from '96-01, I did multiple sets of WUPs, multiple missilex trips to Rosie Roads, and 2 major deployments. I didn't need to read lessons learned for the 2nd trip, because I'd done the first one.
Maybe the Navy needs to break the cycle.
The log side has similar database for port visit reports which is really useful, but usually doesn't get used as part of planning unless you push for it.I think we need to differentiate experience (which we need as well) from lessons learned. Lessons learned as far as I understand it is learning from others experience.
The section that does this better then anyone is the Nav side. The navigators are constantly looking into their notes from other navigators on ports, challenges, rules and lessons from their deployments. Its litterally part of their planning process when they start putting electronic pencil to charts.