Jump to content

HNoMS Helge Ingstad (F313): Difference between revisions

From Wikipedia, the free encyclopedia
Browse history interactively
← Previous editNext edit →
Content deleted Content added
VisualWikitext
The sources is in this wikipedia section, have not spelled out if the lookouts made at least one mistake. The latest source tells about interaction on the bridge between one male and two females
Romnempire (talk | contribs)
259 edits
m damages > compensation. case was settled, not decided.
Line 115: Line 115:
The Ministry of Defence has accepted paying a fine of ten million [[Norwegian kroner]].<ref>{{cite web |last1=Berglund |first1=Nina |title=Duty officer blamed for frigate fiasco |url=https://www.newsinenglish.no/2023/01/17/duty-officer-blamed-for-frigate-fiasco/ |publisher=NewsInEnglish.no |access-date=25 January 2023}}</ref>
The Ministry of Defence has accepted paying a fine of ten million [[Norwegian kroner]].<ref>{{cite web |last1=Berglund |first1=Nina |title=Duty officer blamed for frigate fiasco |url=https://www.newsinenglish.no/2023/01/17/duty-officer-blamed-for-frigate-fiasco/ |publisher=NewsInEnglish.no |access-date=25 January 2023}}</ref>


In 2022, damages were paid to the Ministry of Defence; Norwegian kroner 235 million were paid by the owner ([[Twitt Navigation]] Ltd), of the tanker.<ref name=NotFishFarm/>
In 2022, compensation was paid to the Ministry of Defence as part of a settlement agreement; Norwegian kroner 235 million were paid by the owner ([[Twitt Navigation]] Ltd), of the tanker.<ref name=SettlementCompensation>https://www.aftenposten.no/norge/i/34KBMP/forlik-i-soeksmaal-om-helge-ingstad-havariet-rederi-maa-betale-235-millioner-kroner-til-staten [[Aftenposten]].no.</ref>


====Courtcase====
====Courtcase====

Revision as of 02:29, 31 January 2023

Helge Ingstad in 2010
History
Norway
NameHelge Ingstad
NamesakeNorwegian explorer Helge Ingstad
Ordered23 June 2000
BuilderNavantia, Ferrol
Laid down28 April 2006
Launched23 November 2007
Commissioned29 September 2009
Decommissioned24 June 2019[1]
Stricken13 November 2018
Identification
FateSold for scrap[2]
General characteristics
Class and typeFridtjof Nansen-class frigate
Displacement5,290 long tons (5,370 t)
Length133.2 m (437 ft 0 in)
Beam16.8 m (55 ft 1 in)
Draft7.6 m (24 ft 11 in)
Propulsion
Speed26 knots (48 km/h)
Range4,500 nautical miles (8,300 km)
Complement
  • 120, accommodations for 146
  • Lockheed Martin AN/SPY-1F 3-D multifunction radar
  • Reutech RSR 210N air/sea surveillance radar
  • Sagem Vigy 20 Electro Optical Director
  • MRS 2000 hull mounted sonar
  • Captas MK II V1 active/passive towed sonar
  • 2 × Mark 82 fire-control radar
Electronic warfare
& decoys		Terma DL-12T decoy launcher, Loki torpedo countermeasure
Armament
Aircraft carried1 × NH90 helicopter

HNoMS Helge Ingstad was a Fridtjof Nansen-class frigate of the Royal Norwegian Navy. The vessel was ordered on 23 June 2000 and constructed by Navantia in Spain. The ship was launched on 23 November 2007 and commissioned on 29 November 2009. Named for Helge Ingstad, a Norwegian explorer, the Fridjtof Nansen class are capable of anti-air, anti-submarine and surface warfare. On 8 November 2018, HNoMS Helge Ingstad was in collision with the tanker Sola TS in Norwegian waters just outside Sture Terminal.[3] Helge Ingstad was severely damaged in the collision and beached. On 13 November 2018, the ship sank where she had run aground and became a constructive total loss.[4]

She was raised in a salvage operation from 27 February 2019 to 3 March 2019. In June 2019 after it was deemed uneconomical to repair her, it was decided that she would be scrapped.[5]

Design and description

The design of the Fridtjof Nansen-class frigates began in 1997. Based on the Alvaro de Bazan-class design, Izar (later Navantia) of Spain and Lockheed Martin were chosen to construct the vessel. The class is designed for operational flexibility with each ship capable of anti-air, anti-submarine and surface warfare. This was done to allow vessels of the class to operate with more ease in international operations.[6] The Fridtjof Nansen-class frigates measure 133.2 m (437 ft 0 in) long overall with a beam of 16.8 m (55 ft 1 in) and a draught of 4.9 m (16 ft 1 in). The frigates have a standard displacement of 5,290 long tons (5,370 t).[7]

The frigates are propelled by one 1,360-horsepower (1,010 kW) bow thruster and two controllable pitch propellers powered by a CODAG system with one GE LM2500 gas turbine rated at 26,112 hp (19,472 kW) and two Bazán Bravo 12V diesel engines rated at 12,240 hp (9,130 kW). This gives the frigates a maximum speed of 26 knots (48 km/h; 30 mph) and a range of 4,500 nautical miles (8,300 km; 5,200 mi) at 16 knots (30 km/h; 18 mph). The ships are fitted with a landing pad for one NH90 helicopter.[7]

The class are armed with an octuple launcher for Kongsberg Naval Strike Missiles for surface warfare. The launcher is located amidships, behind the forward superstructure. For anti-air warfare, the Fridjtof Nansens are equipped with an octuple American Mk 41 vertical launch system for 32 RIM-162 ESSM surface-to-air missiles located ahead of the forward superstructure and aft the single-mounted 76 mm (3 in) OTO Melara Super Rapid gun. The ships also mount two twin-mounted 324 mm (12.8 in) torpedo tubes for Sting Ray torpedoes, each mount slotted amidships on either side of the aft superstructure.[7] The frigates also mount depth charges,[6] four 12.7 mm (0.50 in) Browning M2HB heavy machine guns, four Protector (RWS) (Sea PROTECTOR) and two Long Range Acoustic Devices.[citation needed]

For sensors, the frigates are equipped with a Lockheed Martin AN/SPY-1F 3-D multi-function radar, Reutech RSR 210N air/sea surveillance radar, Safran VIGY 20 electro-optical director, MRS 2000 hull-mounted sonar, Captas MK II V1 active/passive towed sonar and two Mark 82 fire-control radar. The Fridjtof Nansen class use the Aegis combat system and Link 11 and is fitted for Link 16/22 combat data systems. For signal defence, the class operates the Terma DL-12T decoy launcher and Loki torpedo countermeasure systems. [7] The vessels have a complement of over 120 personnel.[7][6]

Construction and service

The ship was ordered for construction on 23 June 2000 by Norway and built by the Spanish shipbuilders Navantia at Ferrol, Spain.[7] The vessel was the fourth of the Fridtjof Nansen class to be constructed,[8] and was laid down on 28 April 2006. Construction had been delayed by disputes over quality control. The frigate was launched on 23 November 2007 and named for the Norwegian explorer Helge Ingstad.[7] Helge Ingstad was commissioned in the Royal Norwegian Navy on 29 September 2009.[9]

From December 2013 to May 2014, Helge Ingstad was one of the escort ships for merchant vessels carrying chemical weapons from Syria to be destroyed.[10] In August 2017, she joined Exercise Saxon Warrior off the coast of Scotland, escorting the aircraft carriers HMS Queen Elizabeth of the Royal Navy and USS George H. W. Bush of the United States Navy.[11]

Helge Ingstad in Norway's Sørfjord in June 2018

Collision with oil tanker

On 8 November 2018, while returning from a NATO exercise, she was navigating inshore waters north of Bergen at speeds of up to 17.4 knots (32.2 km/h; 20.0 mph). Starting from around 03:40 there was a watch handover on board Helge Ingstad, during which three oncoming vessels were noted. After radio communication was established, and upon being asked to alter course to starboard, to avoid the 250-metre (820 ft), 112,939 t, Maltese-flagged oil tanker Sola TS, escorted by VSP Tenax, which had just left its berth, Helge Ingstad believed the vessel calling them to be one of the oncoming vessels they were tracking on radar. Assuming the tanker, slow moving and with its bright deck lights obscuring its navigation lights, to be part of the shore installation, the frigate intended to pass it before altering course moving near her starboard channel margin. By the time they realised their error they were within 400 metres (440 yd) of Sola TS and it was too late to avoid a collision.[12] Preben Ottesen, the ship's commanding officer, stated that he was asleep in his cabin when the collision happened, and was in fact awakened by the collision.[13]

The collision caused severe damage to Helge Ingstad, which lost control of engine and steering, with a large breach along her side from the starboard torpedo launchers to the stern. The vessel grounded and continued to take on water, through the propeller shaft and stuffing boxes.[12] Seven sailors were injured in the incident. By late morning she had developed a severe list to starboard with most of the stern submerged.[14][15] Despite damage control efforts the vessel sank in the early hours of 13 November, with only small sections of the superstructure remaining above water.[16] The failure of the vessel's watertight integrity led to an immediate safety alert to designers Navantia, calling on them to advise operators of similar vessels on any necessary measures to address safety, however, a possible design flaw at Navantia was dismissed, as the accident report points to a succession of human failures.[17] This is the first incident of such scale in the Royal Norwegian Navy since 1994, when HNoMS Oslo was lost after it ran aground.[18]

Unlike Helge Ingstad, Sola TS only suffered minor damages in its front and was never in danger of sinking. She was able to continue to her destination after the incident. The tanker subsequently sailed to a shipyard in Gdańsk for repairs and was back in regular service by late December 2018.[19]

Following the frigate's sinking, a local fish farming company, which had had to move fish from the area due to spill of diesel oil from the vessel, claimed one million kroner (US$ 116,000) in damages from the Ministry of Defence.[20]

Salvage operations

The Norwegian Navy inspected Helge Ingstad by the Norwegian Blueye Pioneer underwater drone.[21] Poor weather hampered salvage operations through December 2018; with the planned date to raise the ship being delayed until late January 2019.[22]

The lifting operation began on 26 February 2019.[23][24] On 27 February 2019, due to weather concerns, the partially raised ship was moved to a location which is better protected from the elements, where further salvage work took place.[25] The ship and the two heavy lift vessels (Rambiz and Gulliver) reached the Semco Maritime yard at Hanøytangen on 28 February 2019.[26][27] Boarding parties consisting of some 300 people, including around 100 members of Helge Ingstad's original crew, assisted in pumping out the remaining water so that the ship could be placed on a barge and fully salvaged.[28][29] Helge Ingstad was successfully placed on Boa barge 33 on 2 March 2019[30][23] and arrived at the Haakonsvern naval base on 3 March 2019,[25][31] for removal of spare parts and sensitive equipment.[32]

On 14 May 2019 it was reported the cost of repairing Helge Ingstad would exceed US$1.4 billion, according to the Norwegian Armed Forces, implying that it would be nearly three times cheaper to build a new ship. However, restarting production for just one ship could result in a disproportionally high per-ship cost.[33][34] In January 2021, the Norwegian government signed a 60 million kr (almost $7 million) contract with Norscrap West for the ship's scrapping.[35] The scrapping process was used to learn how to scrap the other Fridtjof Nansen-class vessels in the future.[32]

Investigation, fine for the Ministry of Defence; damages paid, and courtcase

The Norwegian Safety Investigation Authority (NSIA) and the Defence Accident Investigation Board Norway (DAIBN) immediately began a joint investigation, with the involvement of the Marine Safety Investigation Unit of Malta.[36] On 29 November 2018 the AIBN published their preliminary accident report together with two interim safety recommendations. It recommended that the Norwegian military authorities investigate the findings of the preliminary report with a view to implementing any necessary safety measures, and that the shipbuilder Navantia investigate relevant aspects of the design of the frigate and whether other ships might be similarly affected. The watertight condition of the ship was supposedly guaranteed by the 13 watertight bulkheads. Seven compartments were damaged as a result of the collision but initially the ship remained afloat. No one intervened to break the chain of errors. If the commander had observed International Regulations for Preventing Collisions at Sea (COLREGS) the collision would not have occurred.[17]

The second accident report by the Norwegian Safety Investigation Authority (Statens Havarikommisjon) delivered on the 21 April 2021 did exonerate Navantia: the ship suffered damage "above that for which it was designed", and did not make any recommendations for the ship builder.[37] The report mentioned that "If the crew had been better trained, they would have had a better understanding of how to save the ship", and "They didn't understand that various systems were still functioning", noting that the crew evacuated the ship without closing doors, hatches, and other openings that would have maintained stability and buoyancy, avoiding the capsizing and sinking of the vessel, and saving the ship from total loss.[38]

The Ministry of Defence has accepted paying a fine of ten million Norwegian kroner.[39]

In 2022, compensation was paid to the Ministry of Defence as part of a settlement agreement; Norwegian kroner 235 million were paid by the owner (Twitt Navigation Ltd), of the tanker.[40]

Courtcase

Charges were filed in May 2022,[41] and the courtcase started in January 2023, in Hordaland District Court. The defendant is the conning officer - also referred to as officer of the watch (vaktleder) - at the time of the accident.[42] That officer testified in court that he entered the bridge, and proceeded to the map room.[42] Furthermore, he and the officer he was about to relieve had discussed an object that had an "AIS marking that could not be determined"; the tanker had two tugboats near it, therefore the AIS marking [as perceived from a display] was not recognized as anything, except a stationary object, pehaps an oil platform.[43] When the defendant took the conn at 03.53, he gave the entire (bridge team or) crew, a status report: three approaching vessels ahead on the port side, and an illuminated stationary object on the starboard side; he added "Notify me if there is any change [on that situation or] regarding that picture"; furthermore, he testified, at that point the others on the bridge could have given feedback if they had a different opinion; furthermore, he never got any indication from the others on the bridge that the object had left the pier.[44]

Furthermore, "one of us [on the bridge]" commented that it might be a [ oil platform[43] or] platform or an installation for fish farming.[42] The conning officer did not use the radar display to observe the object, and he did not order anyone else to do so.[44][42] Furthermore, the starboard lookout had returned to the bridge at 03.59 (two minutes before the collision); that lookout had not been replaced on the bridge, while the lookout was on a break (a "food-break"). [45] Testimony in court, said that the helmsman recognized the object as a [maritime] vessel, however he was not asked (while on the bridge); he thought the defendant had the same perception about the (oncoming) vessel.[42] Furthermore, the defendant was during his watch, also giving instruction to a female U.S. Navy officer that was on the bridge; she was there as part of her (potential) qualifying for "Officer of the Watch"; furthermore, having to train anyone, is "an element that does distract", he added.[46] Furthermore, the defendant was asked about four of the bridge team members having impaired vision (nedsatt syn) - two of those persons did not fullfill the criteria for such duties, because of their (impaired) vision: The defendant had known nothing about that matter (at the time of the accident).[47]

A new witness at the trial, was the officer of the watch, who the defendant had relieved (on the bridge); That witness said that during the handover of the watch, he and the defendant discussed what the lights were: "Where they (from) fish farming? Or an offshore installation?"; Furthermore, the witness said that they did not think that the lights were from a vessel; Furthermore, the witness did not think that fish farming would be located that close to Stureterminalen.[48] Furthermore, at 03.45, the tanker broadcast on VHF radio, that it (the tanker, now) was departing Stureterminalen; furthermore, the witness testified that he (the witness) was responsible for not having caught the message (on the specific channel that he was duty-bound to listen to, (while on duty) when the warship was in a specific area; furthermore, he testified that if he (the witness) had done his duty by catching the radio transmission, then the (verbal) situation report that he passed on to the defendant, would have left no doubt that the tanker was in motion.[49]

On 28 January 2023, media told about the content of a report, that has not been released to the public (but has been referred to, during the trial); That 42 page report tells about the Norwegian Navy's view of what happened on the tanker's bridge:

  • They[50] did not use radar in the correct manner - neither before or after departure from Stureterminalen; the use was not in accordance with the International Regulations for Preventing Collisions at Sea.
  • The actions of the lookouts, were not in accordance with instructions onboard the tanker, or in accordance with the rules of the International Regulations for Preventing Collisions at Sea.[50]
  • The Norwegian Navy says that the bridge team of the tanker, made a total of 12 mistakes.[50]

Later that month, testimony in court was given by (other) bridge team members of the warship; the female U.S. Navy officer (she testified via a video link), and the two lookouts; furthermore, both lookouts testified that the trainee for the "Officer of the Watch" (the U.S. Navy officer) - she was the one who approved that the lookouts could (one at a time) take [a] short "food break" in the minutes before the accident; furthermore, one lookout was male and the other female.[51]

The helmsman and the Norwegian Navy's foremost[50] expert on navigation at sea (Stein Egil Iversen), are some of the more[48] than 30 witnesses that have been scheduled to testify during the trial.[46]

References

  1. ^ "Ministry confirms frigate scrapping". www.newsinenglish.no.
  2. ^ "Fregatten Helge Ingstad er nå historie". Forsvarsmateriell.no. Norwegian Defence Materiel Agency. Retrieved 6 March 2022.
  3. ^ NRK (8 November 2018). "Tankskipet hadde los og eskortebåt". Retrieved 8 November 2018.
  4. ^ "Britannia P&I faces rising claims picture after frigate". TradeWinds - Latest shipping and maritime news. 13 November 2018. Retrieved 2 March 2019.
  5. ^ Scott, Richard (25 June 2019). "Norway to scrap damaged frigate". janes.com. Retrieved 12 October 2019.
  6. ^ a b c "Fridtjof Nansen-class". Royal Norwegian Navy. Retrieved 15 June 2019.
  7. ^ a b c d e f g Saunders 2009, p. 568.
  8. ^ "Fregatt – Nansenklassen" (in Norwegian). Forsvaret. 6 June 2014. Retrieved 20 November 2016.
  9. ^ "Helge Ingstad (10/2009)". Maritimt Magasin. 10 November 2009.
  10. ^ NTB (29 December 2013). ""Helge Ingstad" i posisjon utenfor Syria". Bergens Tidende (in Norwegian). Retrieved 7 February 2014.
  11. ^ "Multinational Partners on Exercise Saxon Warrior". Royal Navy. 10 August 2017. Retrieved 7 December 2020.
  12. ^ a b "Interim safety recommendations 29.11.2018". Accident Investigation Board Norway. 29 November 2018. Retrieved 8 December 2018.
  13. ^ "Frigate's captain finally speaks out". www.newsinenglish.no. Retrieved 2 March 2019.
  14. ^ "Tankskip og fregatt kolliderte ved Øygarden – krigsskipet mistet styringen" [Tankers and frigates collided at Øygarden - the warship lost control]. Aftenposten (in Norwegian). Retrieved 8 November 2018.
  15. ^ "Norwegian frigate collides with tanker after Trident Juncture". navaltoday.com. Retrieved 8 November 2018.
  16. ^ Nilsen, Thomas (13 November 2018). "Latest: Frigate "Helge Ingstad" sinks". The Barents Observer. Retrieved 13 November 2018.
  17. ^ a b "Interim safety recommendations 29.11.2018 (appendix)". Accident Investigation Board Norway. 29 November 2018. Retrieved 8 December 2018.
  18. ^ Ekanger, Anders. "20 år siden KNM "Oslo" grunnstøtte". NRK (in Norwegian Bokmål). Retrieved 28 November 2018.
  19. ^ "Sola TS ferdig reparert – seiler mot St. Petersburg" [Sola TS has finished repairs - sails towards Saint Petersburg]. Aftenposten (in Norwegian). Retrieved 19 July 2019.
  20. ^ "Fish farmer seeks compensation from Norwegian navy after frigate collision - Xinhua - English.news.cn". www.xinhuanet.com. Archived from the original on 12 January 2019. Retrieved 2 March 2019.
  21. ^ Blueye Robotics (19 December 2018), The Norwegian Navy piloting the Blueye Pioneer underwater drone | Frigate Helge Ingstad, retrieved 25 February 2019
  22. ^ "Salvage Work Resumes for the Wreck of the Helge Ingstad". The Maritime Executive. Retrieved 2 March 2019.
  23. ^ a b Jensen, Adrian Broch (4 March 2019). "Forsvaret: Skjebnen til "Helge Ingstad" kan avgjøres om et par måneder". Tu.no. Teknisk Ukeblad.
  24. ^ Reuters, Christopher Woody. "Norway has begun raising the elite warship that sank after getting rammed by an oil tanker". Business Insider. Retrieved 2 March 2019. {{cite web}}: |last= has generic name (help)
  25. ^ a b "HNoMS Helge Ingstad salvage a success as frigate arrives at Haakonsvern naval base". Naval Today. 4 March 2019.
  26. ^ "Photographs and a video of the Helge Ingstad Salvage released on Thursday 28 February – Heavy Lift News". www.heavyliftnews.com. Retrieved 2 March 2019.
  27. ^ "Salvaged KNM Helge Ingstad Arrives at Semco". MarineLink. 1 March 2019. Retrieved 2 March 2019.
  28. ^ "Salvors Begin Assessment of Wrecked Norwegian Frigate". The Maritime Executive. Retrieved 2 March 2019.
  29. ^ Seglsten, Per Helge; Stensvold, Tore; Nilsen, Jannicke; Urke, Eirik Helland; Jensen, Adrian Broch; Fenstad, Arne (6 February 2019). "Boabarge 33 gjør seg klar til å løfte Helge Ingstad nå". Tu.no. Teknisk Ukeblad. Retrieved 2 March 2019.
  30. ^ "Tu.no". Tu.no.
  31. ^ "KNM "Helge Ingstad" er endelig tilbake på Haakonsvern". www.vg.no.
  32. ^ a b Valle, Marius (11 October 2021). "Fregatten ender som armeringsjern". Tu.no (in Norwegian). Teknisk Ukeblad.
  33. ^ "BT: Reparasjonene av KNM "Helge Ingstad" vil koste 12 milliarder". www.vg.no.
  34. ^ "Report: Cost to Repair Wrecked Norwegian Frigate Exceeds $1.4B". The Maritime Executive.
  35. ^ Fiorenza, Nicholas (18 January 2021). "Norway scraps frigate Helge Ingstad". Archived from the original on 20 January 2021.
  36. ^ "Investigation of marine accident, collision outside the Sture Oil Terminal in Hjeltefjorden, Norway". Accident Investigation Board Norway. Retrieved 7 December 2018.
  37. ^ "Norway exonerates Navantia from sinking a frigate of its Navy". PledgeTimes. 21 April 2021. Retrieved 22 April 2021.
  38. ^ Berglund, Nina (21 April 2021). "Crew could have saved their frigate". NEWSinENGLISH.no. Retrieved 22 April 2021.
  39. ^ Berglund, Nina. "Duty officer blamed for frigate fiasco". NewsInEnglish.no. Retrieved 25 January 2023.
  40. ^ https://www.aftenposten.no/norge/i/34KBMP/forlik-i-soeksmaal-om-helge-ingstad-havariet-rederi-maa-betale-235-millioner-kroner-til-staten Aftenposten.no.
  41. ^ https://www.vg.no/nyheter/innenriks/i/JxeRo6/helge-ingstad-havariet-fregattens-vaktsjef-tiltalt-for-uaktsomhet. Vg.no. Retrieved 6 May 2022
  42. ^ a b c d e https://www.nrk.no/vestland/fregatten-knm-_helge-ingstad_-1.14284192#1.16262585.1.16262585. NRK.no. Retrieved 2023-01-19
  43. ^ a b https://forsvaretsforum.no/forlis-forsvaret-helge-ingstad/ingstad-vaktsjefen-fortalte-om-mareritt-om-kollisjonsoyeblikket/305280. Forsvaretsforum.no
  44. ^ a b https://www.nrk.no/vestland/_helge-ingstad_-rettssaka_-vaktsjefen-orka-ikkje-hoyre-pa-lydloggen-etter-ulukka-1.16262563. NRK.no. Retrieved 2023-01-19
  45. ^ https://www.nrk.no/vestland/fregatten-knm-_helge-ingstad_-1.14284192#1.16262585.1.16262585. NRK.no. "Men logger fra KNM «Helge Ingstad» viser at utkikksposten på styrbord side var ubemannet fra 03.41 og frem til 03.59, to minutter før kollisjonen. Vedkommende hadde tatt spisepause."
  46. ^ a b https://www.aftenposten.no/norge/i/nQv5ao/vaktsjefen-paa-helge-ingstad-det-ville-ha-vaert-mulig-aa-unngaa-ulykken. Aftenposten. Retrieved 2023-01-24
  47. ^ https://www.aftenposten.no/norge/i/nQv5ao/vaktsjefen-paa-helge-ingstad-det-ville-ha-vaert-mulig-aa-unngaa-ulykken. Aftenposten.no. Retrieved 2023-01-25
  48. ^ a b https://www.aftenposten.no/norge/i/kEQ3QX/vaktsjef-paa-helge-ingstad-om-lydopptak-fra-ulykken-jeg-opplevde-det-som-helt-forferdelig. Aftenposten.no. Retrieved 2023-01-25
  49. ^ https://www.nrk.no/vestland/_helge-ingstad_-rettssaken_-avtroppende-vaktsjef-hadde-lytteplikt_-men-horte-ikke-tankskipet-1.16270339. NRK.no. Retrieved 2023-01-26
  50. ^ a b c d https://www.nrk.no/vestland/hemmeligholdt-forsvarsrapport-om-_helge-ingstad_-ulykken_-peker-pa-flere-feil-pa-_sola-ts_-1.16272600. NRK.no. Retrieved 2023-01-28
  51. ^ https://www.nrk.no/vestland/_helge-ingstad_-rettssaka_-amerikansk-offiser-gjekk-i-sjokk-og-matte-fjernast-fra-brua-1.16277190. NRK.no. Retrieved 2023-01-30
Wikimedia Commons has media related to F313 Helge Ingstad (ship, 2007).
Retrieved from "https://en.wikipedia.org/w/index.php?title=HNoMS_Helge_Ingstad_(F313)&oldid=1136587141"