Collision with HMAS Melbourne[edit]
At around 0300 on 3 June 1969, Frank E. Evans was operating in darkness in the South China Sea between Vietnam and Spratly Island in a formation with ships of the Royal Navy, Royal Australian Navy, and Royal New Zealand Navy. All ships in the formation were running without lights. The Royal Australian Navy aircraft carrier Melbourne was in the process of going to flying stations and radioed Frank E. Evans, then to port of her, to take up station as the rescue destroyer. This required Frank E. Evans to reduce speed and take up station on Melbourne′s port quarter. The commanding officer of Frank E. Evans was asleep in his quarters, having left instructions to be awakened if there were to be any changes in the formation. Neither the officer of the deck nor the junior officer of the deck notified him when the station change was ordered. The bridge crew also did not contact the combat information center to request clarification of the positions and movements of the surrounding ships.[10]
The conning officer on Frank E. Evans misunderstood the formation’s base course and believed Frank E. Evans was to starboard of Melbourne. Frank E. Evans therefore turned to starboard, cutting across Melbourne′s bow twice in the process. Melbourne struck Frank E. Evans at a point about 92 feet (28 m) from her bow on her port side and cut her in two at 8°59.2′N 110°47.7′E.[11] After the collision, Frank E. Evans′s bow drifted off to the port side of Melbourne and sank in less than five minutes, taking 73 of her crew with it. One body was recovered from the water, making a total of 74 dead.[12] Her stern scraped along the starboard side of Melbourne, and Melbourne′s crew attached lines to it. It remained afloat. Around 60 to 100 men were rescued from the water.
Decommissioning and disposal[edit]
Frank E. Evans was decommissioned at Subic Bay and stricken from the Naval Vessel Register on 1 July 1969.[13][14] The stern section was sunk as a target in Subic Bay on 10 October 1969.
from Blogger https://ift.tt/VvAyh3t
via IFTTT