Front Matter
January 25, 2008
The Marine Casualty and Pollution Database contains data related to marine casualty investigations reportable under 46 C.F.R. 4.03 and pollution investigations reportable under 33 C.F.R. 153.203. The data reflect information collected by U.S. Coast Guard personnel concerning vessel and waterfront facility accidents and marine pollution incidents throughout the United States and its territories.
In December 2001, the U.S. Coast Guard transitioned from the Marine Safety Information System (MSIS) to the Marine Information for Safety and Law Enforcement (MISLE) system. MISLE changed the way the U.S. Coast Guard collects data. New data elements were added to collect information on new and expanded missions of the U.S. Coast Guard. Many of the tables from MSIS were altered for more efficient database design. The current Casualty and Pollution database has little resemblance to the Casualty and Pollution database derived from MSIS files. New records layouts are provided in this instruction.
Nine files have been added to the CD-ROM. These files contain data from mid December 2001 through January 2008. In addition, over 1,300 casualty and pollution investigations not
included in the 2001 Casualty and Pollution database are part of the new MISLE pollution and casualty database. These cases were open at the time of the 2001 extract and mostly reflect cases from 2000 and 2001 time period. A new vessel and facility file was developed and is included on the CD-ROM. The data in the vessel and facility files date back to 1982. New vessel and facility identifiers were created and should be used in place of the older vessel and facility key fields (vkey/fkey).
Beginning in 2002, Casualty and Pollution investigations are no longer identified by marine casualty case numbers (MC########). MC Case Numbers have been replaced with activity Ids. Activities may be bundled into cases. These cases represent associates between activities. For instance, a marine pollution incident activity may have a follow up incident management activity. Together, these activities represent a case.
Your CD-ROM has an activity file that contains common data for casualty and pollution activities. The file contains the incident date, the unit that conducted the investigation and any associated case numbers. All activities in the database are closed investigations. Below are the number of open Pollution and Injury/Death Investigations not included on the CD-ROM.
| CY 2002 |
212 |
| CY 2003 |
187 |
| CY 2004 |
264 |
| CY 2005 |
481 |
| CY 2006 |
3,841 |
| CY 2007 |
3,834 |
| CY 2008 |
173 |
| CY 2002 |
11 |
| CY 2003 |
89 |
| CY 2004 |
88 |
| CY 2005 |
173 |
| CY 2006 |
1,011 |
| CY 2007 |
859 |
| CY 2008 |
17 |
| CY 2002 |
28 |
| CY 2003 |
50 |
| CY 2004 |
57 |
| CY 2005 |
170 |
| CY 2006 |
1,281 |
| CY 2007 |
1,472 |
| CY 2008 |
70 |
| CY 2002 |
194 |
| CY 2003 |
319 |
| CY 2004 |
425 |
| CY 2005 |
1,344 |
| CY 2006 |
7,785 |
| CY 2007 |
9,830 |
| CY 2008 |
519 |
The material is predecisional and is not releasable to the public. When these activities are closed, they will be included in future releases.
The vessel and facility event tables contain the event timeline in a casualty or pollution incident. Some casualties have multiple events and can involve both vessels and facilities. Use the activity id in these files as the join field to the other tables in the database.
A separate table with details on personnel injury events is included on the CD-ROM. This table contains details on injuries to crewmembers, passengers and other parties.
There are three pollution tables included on the CD-ROM. These tables provide details on marine pollution events involving vessels, facilities and other pollution sources. These pollution tables have similar data structures and provide details on the substance and the amount of the discharge. To find information on a vessel pollution event, see the MisleVslPoll table. Details on facility pollution events are located in the MisleFacPoll table. Information on other pollution sources is contained in the MisleOtherPoll table (i.e., automobiles). For more information on
the pollution source, refer to the vessel and facility tables. The join field for these tables is vessel/nonvessel id.
Information on mystery spills and ticket cases is included in the pollution tables. Mystery spills are defined as a waterway condition because the source of the spill is unknown and may appear in any of the three pollution tables. Ticket cases are included in the database. These cases are assigned activity numbers and replace the old MSIS ticket numbers (TK########).
A new vessel and facility table is provided on the CD-ROM that provides details on over 936,800 vessels and 42,200 facilities. Many of these records were created in MSIS and migrated to MISLE. A new vessel/nonvessel id was created to replace the VKEY/FKEY used in MSIS. These tables were constructed to include many of the same data elements in past MSIS vessel and facility tables. When the U.S. Coast Guard performs activities on vessels and facilities, new records are entered or updated in the system to reflect changes in the vessel or facility’s service
Hints on joining files. The activity identifiers are computer-generated numbers identifying an investigation activity. Each activity has subcategories to further define the activity. Each file in the database contains an activity identifier that can be joined across files. By joining these files, more details on the investigation case are supplied.
A facility and vessel file are included on the CD-ROM to provide you with details on vessels and facilities involved in a marine casualty. To join the vessel and
facility files to the other database files, join the gk_d_vessel or gk_d_facility fields to the vessel_id and nonvessel_id ids in the other subject files.
Not included on the CD-ROM is the file that lists other sources of pollution. Other sources include aircraft, vehicles, and other facilities not classified in the
facility file.
Questions concerning the data should be directed to Mr. Harold Krevait at (202)372-1289.
Entity Attributes
Table Name: MisleActivity
| 1 |
int |
activity_id |
4 |
| 2 |
int |
case_id |
4 |
| 3 |
char |
incident_dt |
10 |
| 4 |
char |
dept_name |
40 |
| 5 |
varchar |
activity_type |
25 |
| 6 |
varchar |
activity_status |
25 |
| 7 |
varchar |
activity_status_subtype |
50 |
Table Name: MisleFacEvents
| 1 |
int |
activity_id |
4 |
| 2 |
int |
case_id |
4 |
| 3 |
char |
incident_dt |
10 |
| 4 |
varchar |
activity_type |
22 |
| 5 |
int |
nonvessel_id |
4 |
| 6 |
varchar |
waterway_name |
50 |
| 7 |
varchar |
event_type |
30 |
| 8 |
varchar |
event_class |
46 |
| 9 |
varchar |
event_subclass |
55 |
| 10 |
varchar |
activity_role |
47 |
| 11 |
varchar |
damage_status |
38 |
| 12 |
varchar |
latitude |
21 |
| 13 |
varchar |
longitude |
22 |
Table Name: MisleVslEvents
| 1 |
int |
activity_id |
4 |
| 2 |
int |
case_id |
4 |
| 3 |
char |
incident_dt |
10 |
| 4 |
varchar |
activity_type |
22 |
| 5 |
int |
vessel_id |
4 |
| 6 |
varchar |
waterway_name |
50 |
| 7 |
varchar |
event_type |
30 |
| 8 |
varchar |
event_class |
46 |
| 9 |
varchar |
event_subclass |
55 |
| 10 |
varchar |
activity_role |
50 |
| 11 |
varchar |
damage_status |
35 |
| 12 |
varchar |
latitude |
21 |
| 13 |
varchar |
longitude |
22 |
Table Name: MisleInjury
| 1 |
int |
activity_id |
4 |
| 2 |
char |
incident_dt |
10 |
| 3 |
varchar |
activity_type |
22 |
| 4 |
int |
vessel_id |
4 |
| 5 |
varchar |
relationship_type |
25 |
| 6 |
varchar |
waterway_name |
50 |
| 7 |
varchar |
accident_type |
48 |
| 8 |
varchar |
casualty_type_desc |
23 |
| 9 |
varchar |
latitude |
21 |
| 10 |
varchar |
longitude |
22 |
Table Name: MisleFacPoll
| 1 |
int |
activity_id |
4 |
| 2 |
int |
case_id |
4 |
| 3 |
char |
incident_dt |
10 |
| 4 |
varchar |
activity_type |
22 |
| 5 |
int |
nonvessel_id |
4 |
| 6 |
varchar |
waterway_name |
50 |
| 7 |
char |
chris_cd |
3 |
| 8 |
varchar |
substance_name |
98 |
| 9 |
varchar |
substance_class |
11 |
| 10 |
varchar |
substance_subclass |
27 |
| 11 |
varchar |
substance_type |
80 |
| 12 |
varchar |
substance_subtype |
75 |
| 13 |
varchar |
latitude |
21 |
| 14 |
varchar |
longitude |
22 |
| 15 |
decimal |
discharge_amnt_total |
12 dec 1 |
| 16 |
decimal |
discharge_amnt_water |
12 dec 1 |
| 17 |
decimal |
discharge_amnt_land |
12 dec 1 |
| 18 |
decimal |
discharge_amnt_air |
12 dec 1 |
| 19 |
decimal |
discharge_amnt_enclosed |
12 dec 1 |
| 20 |
decimal |
potential_amnt_total |
12 dec 1 |
| 21 |
decimal |
potential_amnt_water |
12 dec 1 |
| 22 |
decimal |
potential_amnt_land |
12 dec 1 |
| 23 |
decimal |
potential_amnt_air |
12 dec 1 |
| 24 |
decimal |
potential_amnt_enclosed |
12 dec 1 |
| 25 |
decimal |
contained_amnt |
12 dec 1 |
| 26 |
varchar |
discharge_potential_type |
11 |
| 27 |
varchar |
discharge_situation_type |
44 |
| 28 |
varchar |
discharge_estimated_land |
11 |
| 29 |
varchar |
discharge_estimated_air |
11 |
| 30 |
varchar |
discharge_estimated_water |
11 |
| 31 |
varchar |
discharge_estimated_encl |
11 |
| 32 |
varchar |
potential_case |
18 |
| 33 |
varchar |
potential_estimated |
11 |
| 34 |
varchar |
contained_estimated |
11 |
| 35 |
varchar |
unit_of_measure |
26 |
| 36 |
varchar |
activity_role |
47 |
| 37 |
varchar |
damage_status |
38 |
Table Name: MisleVslPoll
| 1 |
int |
activity_id |
4 |
| 2 |
int |
case_id |
4 |
| 3 |
char |
incident_dt |
10 |
| 4 |
varchar |
activity_type |
22 |
| 5 |
int |
vessel_id |
4 |
| 6 |
varchar |
waterway_name |
50 |
| 7 |
char |
chris_cd |
3 |
| 8 |
varchar |
substance_name |
98 |
| 9 |
varchar |
substance_class |
11 |
| 10 |
varchar |
substance_subclass |
27 |
| 11 |
varchar |
substance_type |
80 |
| 12 |
varchar |
substance_subtype |
75 |
| 13 |
varchar |
latitude |
21 |
| 14 |
varchar |
longitude |
22 |
| 15 |
decimal |
discharge_amnt_total |
13 dec 1 |
| 16 |
decimal |
discharge_amnt_water |
13 dec 1 |
| 17 |
decimal |
discharge_amnt_land |
13 dec 1 |
| 18 |
decimal |
discharge_amnt_air |
13 dec 1 |
| 19 |
decimal |
discharge_amnt_enclosed |
13 dec 1 |
| 20 |
decimal |
potential_amnt_total |
13 dec 1 |
| 21 |
decimal |
potential_amnt_water |
13 dec 1 |
| 22 |
decimal |
potential_amnt_land |
13 dec 1 |
| 23 |
decimal |
potential_amnt_air |
13 dec 1 |
| 24 |
decimal |
potential_amnt_enclosed |
13 dec 1 |
| 25 |
decimal |
contained_amnt |
13 dec 1 |
| 26 |
varchar |
discharge_potential_type |
11 |
| 27 |
varchar |
discharge_situation_type |
44 |
| 28 |
varchar |
discharge_estimated_land |
11 |
| 29 |
varchar |
discharge_estimated_air |
11 |
| 30 |
varchar |
discharge_estimated_water |
11 |
| 31 |
varchar |
discharge_estimated_encl |
11 |
| 32 |
varchar |
potential_case |
18 |
| 33 |
varchar |
potential_estimated |
11 |
| 34 |
varchar |
contained_estimated |
11 |
| 35 |
varchar |
unit_of_measure |
26 |
| 36 |
varchar |
activity_role |
50 |
| 37 |
varchar |
damage_status |
38 |
Table Name: MisleOtherPoll
| 1 |
int |
activity_id |
4 |
| 2 |
int |
case_id |
4 |
| 3 |
char |
incident_dt |
10 |
| 4 |
varchar |
activity_type |
22 |
| 5 |
int |
other_id |
4 |
| 6 |
varchar |
subject_name |
70 |
| 7 |
varchar |
waterway_name |
50 |
| 8 |
char |
chris_cd |
3 |
| 9 |
varchar |
substance_name |
98 |
| 10 |
varchar |
substance_class |
11 |
| 11 |
varchar |
substance_subclass |
27 |
| 12 |
varchar |
substance_type |
80 |
| 13 |
varchar |
substance_subtype |
75 |
| 14 |
varchar |
latitude |
21 |
| 15 |
varchar |
longitude |
22 |
| 16 |
decimal |
discharge_amnt_total |
12 dec 1 |
| 17 |
decimal |
discharge_amnt_water |
12 dec 1 |
| 18 |
decimal |
discharge_amnt_land |
12 dec 1 |
| 19 |
decimal |
discharge_amnt_air |
12 dec 1 |
| 20 |
decimal |
discharge_amnt_enclosed |
12 dec 1 |
| 21 |
decimal |
potential_amnt_total |
12 dec 1 |
| 22 |
decimal |
potential_amnt_water |
12 dec 1 |
| 23 |
decimal |
potential_amnt_land |
12 dec 1 |
| 24 |
decimal |
potential_amnt_air |
12 dec 1 |
| 25 |
decimal |
potential_amnt_enclosed |
12 dec 1 |
| 26 |
decimal |
contained_amnt |
12 dec 1 |
| 27 |
varchar |
discharge_potential_type |
11 |
| 28 |
varchar |
discharge_situation_type |
44 |
| 29 |
varchar |
discharge_estimated_land |
11 |
| 30 |
varchar |
discharge_estimated_air |
11 |
| 31 |
varchar |
discharge_estimated_water |
11 |
| 32 |
varchar |
discharge_estimated_encl |
11 |
| 33 |
varchar |
potential_case |
18 |
| 34 |
varchar |
potential_estimated |
11 |
| 35 |
varchar |
contained_estimated |
11 |
| 36 |
varchar |
unit_of_measure |
26 |
Table Name: MisleVessel
| 1 |
char |
gk_d_vessel |
28 |
| 2 |
char |
vessel_id |
15 |
| 3 |
varchar |
vessel_name |
50 |
| 4 |
char |
managing_owner_id |
28 |
| 5 |
varchar |
managing_owner |
120 |
| 6 |
varchar |
gross_ton |
8 |
| 7 |
varchar |
net_ton |
8 |
| 8 |
varchar |
length |
7 |
| 9 |
varchar |
breadth |
7 |
| 10 |
varchar |
depth |
7 |
| 11 |
varchar |
itc_breadth |
7 |
| 12 |
varchar |
itc_depth |
7 |
| 13 |
varchar |
itc_gross_ton |
8 |
| 14 |
varchar |
itc_length |
7 |
| 15 |
varchar |
itc_net_ton |
8 |
| 16 |
varchar |
draft_design |
8 |
| 17 |
char |
draft_design_units |
2 |
| 18 |
char |
dead_weight_ton |
8 |
| 19 |
char |
deadweighttonnage_units |
2 |
| 20 |
char |
flag_abbr |
2 |
| 21 |
varchar |
hailing_port |
50 |
| 22 |
varchar |
hailing_port_state |
2 |
| 23 |
varchar |
hailing_port_province |
50 |
| 24 |
varchar |
route_type |
50 |
| 25 |
varchar |
classification_society |
80 |
| 26 |
varchar |
cargo_authorization_type |
30 |
| 27 |
char |
documented_ind |
1 |
| 28 |
varchar |
documented_status_type |
30 |
| 29 |
char |
inspected_ind |
1 |
| 30 |
varchar |
inspected_desc |
30 |
| 31 |
char |
state_vessel_ind |
1 |
| 32 |
varchar |
state_vessel_desc |
30 |
| 33 |
char |
lloyds_ind |
1 |
| 34 |
varchar |
lloyds_desc |
30 |
| 35 |
char |
solas_ind |
1 |
| 36 |
varchar |
solas_desc |
30 |
| 37 |
varchar |
insp_subchapter_type |
255 |
| 38 |
varchar |
vessel_class |
50 |
| 39 |
varchar |
vessel_type |
50 |
| 40 |
varchar |
vessel_subtype |
50 |
| 41 |
varchar |
vessel_service |
30 |
| 42 |
varchar |
max_passengers_allowed |
6 |
| 43 |
varchar |
max_crew |
6 |
| 44 |
varchar |
self_propelled_ind |
1 |
| 45 |
varchar |
propulsion_type |
30 |
| 46 |
varchar |
hull_material |
30 |
| 47 |
varchar |
hull_design_type |
30 |
| 48 |
varchar |
hull_double_bottom_type |
30 |
| 49 |
varchar |
hull_double_side_type |
30 |
| 50 |
varchar |
call_sign |
8 |
| 51 |
varchar |
official_number |
10 |
| 52* |
varchar |
primary_vin |
30 |
| 53 |
varchar |
hull_number |
30 |
| 54 |
varchar |
rbs_hull_number |
30 |
| 55 |
varchar |
imo_number |
30 |
| 56 |
varchar |
vessel_age |
4 |
| 57 |
varchar |
build_shipyard |
50 |
| 58 |
char |
build_year |
4 |
| 59 |
varchar |
hull_build_party_name |
80 |
| 60 |
varchar |
completed_by_party_name |
80 |
| 61 |
varchar |
horsepower_ahead |
5 |
| 62 |
varchar |
horsepower_astern |
5 |
| 63 |
varchar |
forebody_type_desc |
30 |
| 64 |
varchar |
hull_configuration |
30 |
| 65 |
varchar |
hull_shape |
30 |
| 66 |
char |
filler |
1 |
*new field added October 2007
Table Name: MisleFacility
| 1 |
int |
gk_d_facility |
4 |
| 2 |
int |
msn_non_vessel_id |
4 |
| 3 |
varchar |
facility_name |
34 |
| 4 |
varchar |
facility_type_desc |
29 |
| 5 |
varchar |
facility_subtype_desc |
26 |
| 6 |
char |
facility_state_abbr |
2 |
| 7 |
varchar |
nav_hazard_desc |
23 |
| 8 |
varchar |
pollution_source_desc |
22 |
| 9 |
varchar |
public_safety_risk_desc |
24 |
| 10 |
varchar |
primary_id_type_desc |
23 |
| 11 |
varchar |
primary_id |
17 |
| 12 |
varchar |
latitude |
21 |
| 13 |
varchar |
longitude |
22 |
| 14 |
varchar |
manned_platform_desc |
21 |
| 15 |
varchar |
helo_deck_desc |
23 |
| 16 |
varchar |
inspected_facility_desc |
22 |
| 17 |
char |
current_ind |
1 |
| MisleActivity.txt |
36,951 |
| MisleFacEvents.txt |
7,375 |
| MisleVslEvents.txt |
39,053 |
| MisleInjury.txt |
4,872 |
| MisleFacPoll.txt |
5,780 |
| MisleVslPoll.txt |
8,424 |
| MisleOtherPoll.txt |
5,183 |
| MisleVessel.txt |
936,826 |
| MisleFacility.txt |
42,253 |
|