Maritime Legal Engineering Skill
Engineering-technical interface with maritime legal proceedings. Covers casualty investigation, expert witness support, admiralty law reference, and regulatory compliance.
Scope boundary: This skill covers engineering-technical analysis only. It does NOT provide legal advice. All outputs require review by qualified maritime attorneys.
Casualty Investigation Support
Analyze marine casualty reports (MAIB, NTSB, USCG) to:
- Identify ISM Code non-conformities (SMS failures, inadequate procedures)
- Map findings to root-cause taxonomy:
- Equipment failure — material defect, maintenance lapse, design inadequacy
- Human factors — situational awareness, fatigue, communication breakdown
- Weather/environment — sea state beyond design basis, visibility, ice
- SMS failure — procedure not followed, not written, or inadequate
- Cross-reference
worldenergydata.MAIBLoader + NTSBMarineLoader for comparable incidents
Expert Witness Report Structure
For admiralty proceedings produce reports in this order:
- Qualifications — credentials, relevant experience, publications
- Scope and instructions — what was asked; documents reviewed
- Technical background — relevant standards and vessel type overview
- Factual findings — timeline reconstruction; condition of equipment
- Standard of care analysis — what a competent operator would have done
- Causation — proximate cause chain; contributing factors
- Opinion — engineering conclusion framed for legal use
- Limitations — what could not be determined; data gaps
Framing standard: Daubert (US federal/USDC) or Civil Evidence Act 1995 (UK) as applicable.
Admiralty Law Reference
| Instrument |
Scope |
| COLREGs 1972 |
Collision regulations — Rules of the Road |
| Jones Act (46 USC 30104) |
US seaman negligence claims |
| Limitation of Liability Act (46 USC 30505) |
Shipowner liability cap |
| Hague-Visby Rules |
Bill of lading cargo claims |
| MLC 2006 |
Seafarer working and living conditions |
| P&I Club process |
Third-party liability; club letters of undertaking |
Incident Database Query
# Example: find comparable propulsion casualties
from worldenergydata import MAIBLoader, NTSBMarineLoader
maib = MAIBLoader()
results = maib.query(vessel_type="bulk carrier", cause_category="propulsion", year_range=(2015, 2024))
# Returns: incident_id, vessel, date, cause_summary, outcome
Liability Framing
Translate engineering findings into legal causation language:
- Proximate cause — "The immediate cause of the allision was the failure of the bow thruster, which directly caused loss of maneuverability in confined waters."
- Standard of care — "A prudent operator would have tested thruster response before entering the channel per port authority standing instructions."
- Damages estimation — hull repair quote + cargo loss + wreck removal + third-party property; reference comparable settlements where available
Regulatory Framework
| Regulation |
Applicability |
| 46 CFR Parts 90–196 |
US vessel inspection requirements |
| 33 CFR Parts 160–173 |
US navigation and waterways safety |
| SOLAS Chapter II-1/II-2 |
Construction, subdivision, machinery, fire |
| MARPOL Annex I–VI |
Pollution prevention |
| ISM Code (SOLAS IX) |
Safety management systems |
| USCG MISLE |
US marine casualty reporting (CG-2692) |
| BSEE 30 CFR 250 |
OCS incident notifications (offshore) |
1---2name: maritime-legal3description: AI-assisted maritime legal and casualty consulting — engineering-technical interface with admiralty proceedings4---56# Maritime Legal Engineering Skill78> Engineering-technical interface with maritime legal proceedings. Covers casualty investigation, expert witness support, admiralty law reference, and regulatory compliance.9>10> **Scope boundary:** This skill covers engineering-technical analysis only. It does NOT provide legal advice. All outputs require review by qualified maritime attorneys.1112## Casualty Investigation Support1314Analyze marine casualty reports (MAIB, NTSB, USCG) to:15- Identify ISM Code non-conformities (SMS failures, inadequate procedures)16- Map findings to root-cause taxonomy:17 - **Equipment failure** — material defect, maintenance lapse, design inadequacy18 - **Human factors** — situational awareness, fatigue, communication breakdown19 - **Weather/environment** — sea state beyond design basis, visibility, ice20 - **SMS failure** — procedure not followed, not written, or inadequate21- Cross-reference `worldenergydata.MAIBLoader` + `NTSBMarineLoader` for comparable incidents2223## Expert Witness Report Structure2425For admiralty proceedings produce reports in this order:26271. **Qualifications** — credentials, relevant experience, publications282. **Scope and instructions** — what was asked; documents reviewed293. **Technical background** — relevant standards and vessel type overview304. **Factual findings** — timeline reconstruction; condition of equipment315. **Standard of care analysis** — what a competent operator would have done326. **Causation** — proximate cause chain; contributing factors337. **Opinion** — engineering conclusion framed for legal use348. **Limitations** — what could not be determined; data gaps3536Framing standard: Daubert (US federal/USDC) or Civil Evidence Act 1995 (UK) as applicable.3738## Admiralty Law Reference3940| Instrument | Scope |41|-----------|-------|42| COLREGs 1972 | Collision regulations — Rules of the Road |43| Jones Act (46 USC 30104) | US seaman negligence claims |44| Limitation of Liability Act (46 USC 30505) | Shipowner liability cap |45| Hague-Visby Rules | Bill of lading cargo claims |46| MLC 2006 | Seafarer working and living conditions |47| P&I Club process | Third-party liability; club letters of undertaking |4849## Incident Database Query5051```python52# Example: find comparable propulsion casualties53from worldenergydata import MAIBLoader, NTSBMarineLoader54maib = MAIBLoader()55results = maib.query(vessel_type="bulk carrier", cause_category="propulsion", year_range=(2015, 2024))56# Returns: incident_id, vessel, date, cause_summary, outcome57```5859## Liability Framing6061Translate engineering findings into legal causation language:62- **Proximate cause** — "The immediate cause of the allision was the failure of the bow thruster, which directly caused loss of maneuverability in confined waters."63- **Standard of care** — "A prudent operator would have tested thruster response before entering the channel per port authority standing instructions."64- **Damages estimation** — hull repair quote + cargo loss + wreck removal + third-party property; reference comparable settlements where available6566## Regulatory Framework6768| Regulation | Applicability |69|-----------|--------------|70| 46 CFR Parts 90–196 | US vessel inspection requirements |71| 33 CFR Parts 160–173 | US navigation and waterways safety |72| SOLAS Chapter II-1/II-2 | Construction, subdivision, machinery, fire |73| MARPOL Annex I–VI | Pollution prevention |74| ISM Code (SOLAS IX) | Safety management systems |75| USCG MISLE | US marine casualty reporting (CG-2692) |76| BSEE 30 CFR 250 | OCS incident notifications (offshore) |