NTSB Issues Accident Report for 2004 Water Taxi Incident

Tuesday, May 16, 2006
On March 6, 2004, the small passenger vessel Lady D, a pontoon water taxi with 2 crewmembers and 23 passengers on board, was en route from Fort McHenry to Fells Point, Maryland, when it encountered a rapidly developing storm with high winds. The pontoon vessel began to roll in the waves and eventually continued over onto its starboard side and capsized. Personnel from the Naval Reserve Center Baltimore, a Navy training installation adjacent to Fort McHenry, witnessed the capsizing, called 911 to report the accident, and then launched a vessel to the scene to render assistance. Responders were able to rescue or recover all but 3 occupants of the Lady D within an hour of the accident. The bodies of the remaining victims were recovered from the waterway on March 14 and 15. As a result of this accident, 5 passengers died; 4 passengers suffered serious injuries; and 12 people sustained minor injuries. Vessel damage was estimated at $35,000. The Safety Board’s investigation of this accident identified major safety issues in the following areas: • Passenger weight criteria for stability assessment; • Pontoon vessel stability standards; and • Policies and procedures pertaining to weather operations. The National Transportation Safety Board determines that the probable cause of the capsizing of the pontoon-style small passenger vessel Lady D was its lack of intact stability, which was insufficient to withstand the strong winds and waves that the boat encountered. The lack of intact stability was caused by overloading, which resulted from a combination of the following: • The Lady D was erroneously granted sister status by the U.S. Coast Guard to a pontoon vessel with different design characteristics; • The Coast Guard certificated the Lady D to carry too many people as a result of an inappropriate stability test on the vessel to which it was granted sister status; and • The Coast Guard’s regulatory stability test standards on which the Lady D’s passenger allowance was based use an out-of-date average passenger weight. As a result of this investigation, the Safety Board makes recommendations to the U.S. Coast Guard.
Maritime Reporter July 2014 Digital Edition
FREE Maritime Reporter Subscription
Latest Maritime News    rss feeds

Navy

East and South China Sea Disputes Need Creative Diplomacy

China and the United States appear headed for a damaging confrontation over the extent of China's territorial claims in the South and East China Seas. Now that

Darwin, Australia Scene of KAKADU Exercise Planning

Over 1,200 military personnel from the Asia Pacific and Indian Ocean regions have completed collaborative, tactical warfare planning during the first week of the

Navy Autonomous Underwater Vehicle Delivery Milestone

Commander, Submarine Development Squadron 5 (CSDS 5), Detachment UUV, informs of the delivery of Large Training Vehicle 38 (LTV 38), an unmanned undersea vehicle (UUV),

Maritime Safety

Long Beach Cargo Operations Resume

Repair work begins after storm surges subsides The Port of Long Beach resumed full cargo-handling operations Thursday, Aug. 28, after a lessening of storm surges

Ferry Runs Aground in Lynn Harbor

Ferry Cetacea ran aground about a quarter of a mile from the pier in Lynn Harbor, Massachusetts yesterday, with 13 passengers and four crew aboard, the U.S. Coast Guard (USCG) reported.

Helideck Safety System to Launch at SMM

Amarcon and Observator Instruments will develop a helideck monitoring and forecasting system to improve the safety of helicopter landings and take-offs from a vessel.

 
 
Maritime Contracts Maritime Security Maritime Standards Pipelines Port Authority Ship Repair Ship Simulators Shipbuilding / Vessel Construction Sonar Winch
rss | archive | history | articles | privacy | terms and conditions | contributors | top maritime news | about us | copyright | maritime magazines
maritime security news | shipbuilding news | maritime industry | shipping news | maritime reporting | workboats news | ship design | maritime business

Time taken: 0.1591 sec (6 req/sec)