Thank you for correcting the text in this article. Your corrections improve Papers Past searches for everyone. See the latest corrections.

This article contains searchable text which was automatically generated and may contain errors. Join the community and correct any errors you spot to help us improve Papers Past.

Article image
Article image
Article image
Article image

SENSATIONAL STORY OF CREW'S PANIC

(Eeceived 16, 10;50 a,m.) NOEFOLK (Virginia), Nov. 15. Borton Blaaskas, third engineer of the Chandris, told a ^ensational story of the crew's panic befote the disaster. He said that the vessel was leaking badly owing to three days' batterilig hy mountainous seas. The crew demanded that the captain should send an S.O.S. hours before the first signal was Sent. The captain ordered them to return to the pumps, evidently believing that the vessel could ride out the storm, Finally the pumps were swamped. "I went to the radio room and demanded that an S.O.S. should he sent," he added. "The operator refused without the captain 's orders. I drew ft knife and compelled him to obey." Other seamen stated that a berserk member of the crew attacked the captain and bit his face.

Permanent link to this item

https://paperspast.natlib.govt.nz/newspapers/HBHETR19371116.2.48

Bibliographic details

Hawke's Bay Herald-Tribune, Volume 81, Issue 45, 16 November 1937, Page 5

Word Count
138

SENSATIONAL STORY OF CREW'S PANIC Hawke's Bay Herald-Tribune, Volume 81, Issue 45, 16 November 1937, Page 5

SENSATIONAL STORY OF CREW'S PANIC Hawke's Bay Herald-Tribune, Volume 81, Issue 45, 16 November 1937, Page 5

Help

Log in or create a Papers Past website account

Use your Papers Past website account to correct newspaper text.

By creating and using this account you agree to our terms of use.

Log in with RealMe®

If you’ve used a RealMe login somewhere else, you can use it here too. If you don’t already have a username and password, just click Log in and you can choose to create one.


Log in again to continue your work

Your session has expired.

Log in again with RealMe®


Alert