20220715
08220300
1.0
FALSE
TRN_CRASH_DATA
002
Projected
GCS_WGS_1984
Linear Unit: Meter (1.000000)
WGS_1984_Web_Mercator_Auxiliary_Sphere
<ProjectedCoordinateSystem xsi:type='typens:ProjectedCoordinateSystem' xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance' xmlns:xs='http://www.w3.org/2001/XMLSchema' xmlns:typens='http://www.esri.com/schemas/ArcGIS/2.8.0'><WKT>PROJCS["WGS_1984_Web_Mercator_Auxiliary_Sphere",GEOGCS["GCS_WGS_1984",DATUM["D_WGS_1984",SPHEROID["WGS_1984",6378137.0,298.257223563]],PRIMEM["Greenwich",0.0],UNIT["Degree",0.0174532925199433]],PROJECTION["Mercator_Auxiliary_Sphere"],PARAMETER["False_Easting",0.0],PARAMETER["False_Northing",0.0],PARAMETER["Central_Meridian",0.0],PARAMETER["Standard_Parallel_1",0.0],PARAMETER["Auxiliary_Sphere_Type",0.0],UNIT["Meter",1.0],AUTHORITY["EPSG",3857]]</WKT><XOrigin>-20037700</XOrigin><YOrigin>-30241100</YOrigin><XYScale>10000</XYScale><ZOrigin>0</ZOrigin><ZScale>1</ZScale><MOrigin>0</MOrigin><MScale>1</MScale><XYTolerance>0.001</XYTolerance><ZTolerance>0.001</ZTolerance><MTolerance>0.001</MTolerance><HighPrecision>true</HighPrecision><WKID>102100</WKID><LatestWKID>3857</LatestWKID></ProjectedCoordinateSystem>
20220720
14463600
20250618
13370800
150000000
5000
FGDC
Esri ArcGIS 12.8.3.29751
Public Crash Data
2022-08-01T00:00:00
Mark A. Prettyman
Delaware Department of Technology and Information
Software Engineer
Arshon Howard
Delaware Department of Safety & Homeland Security
Chief Community Relations
The purpose of this data is to satisfy the requirements of 21 Del. C. § 313 to make de-identified crash data available to the public
<DIV STYLE="text-align:Left;"><DIV><DIV><P STYLE="text-align:Justify;margin:0 0 0 0;"><SPAN><SPAN>The Delaware Department of Safety and Homeland Security (DSHS) is the official custodian of Delaware crash reports and is responsible for statewide crash data collection and dissemination. A crash report is a summary of information collected about a collision and is filled out by a Delaware law enforcement officer who is investigating the crash. The data contained on FirstMap and the Open Data Portal represents the best available information at DSHS and is not an official record of what transpired in a particular crash or for a particular crash type and does not contain personal information. This data is generated from crash reports and allows any member of the public to engage in interactive analysis and data exploration for the purpose of identifying, evaluating or planning the safety enhancement of potential crash sites, hazardous roadway conditions, or railway-highway crossings. This data is updated monthly and contains crashes that occurred since 2009 through six months ago. Official crash reports are confidential and are not a public record under the Delaware Freedom of Information Act. Authorized parties may contact the reporting police agency directly for official copies of crash reports (21 Del. C. §313).</SPAN></SPAN></P><P STYLE="text-align:Justify;margin:0 0 0 0;"><SPAN><SPAN> </SPAN></SPAN></P><P STYLE="text-align:Justify;margin:0 0 0 0;"><SPAN><SPAN>DSHS is committed to bringing public awareness to crash information. The Office of Highway Safety’s annual reports (</SPAN></SPAN><A href="https://ohs.delaware.gov/reports.shtml" STYLE="text-decoration:underline;"><SPAN STYLE="text-decoration:underline;"><SPAN>https://ohs.delaware.gov/reports.shtml</SPAN></SPAN></A><SPAN><SPAN>), the Office of Highway Safety’s annual safety plan (</SPAN></SPAN><A href="https://ohs.delaware.gov/reports.shtml" STYLE="text-decoration:underline;"><SPAN STYLE="text-decoration:underline;"><SPAN>https://ohs.delaware.gov/reports.shtml</SPAN></SPAN></A><SPAN><SPAN>), and the Delaware State Police Traffic Statistical Reports (</SPAN></SPAN><A href="https://dsp.delaware.gov/reports/" STYLE="text-decoration:underline;"><SPAN STYLE="text-decoration:underline;"><SPAN>https://dsp.delaware.gov/reports/</SPAN></SPAN></A><SPAN><SPAN>) also contain a variety of information and data. In addition, the State of Delaware’s Strategic Highway Safety Plan is available at </SPAN></SPAN><A href="https://deldot.gov/Programs/DSHSP/index.shtml" STYLE="text-decoration:underline;"><SPAN STYLE="text-decoration:underline;"><SPAN>https://deldot.gov/Programs/DSHSP/index.shtml</SPAN></SPAN></A><SPAN> and is updated every five years.</SPAN></P></DIV></DIV></DIV>
Crash
Accident
DSHS
Transportation
SB28
21 Del. C. § 313
Safety
Data range is from 1/1/2009 through 6 months prior to the current month.
2009-01-01T00:00:00
0
-75.788658
-75.048939
38.451013
39.839007
<DIV STYLE="text-align:Left;"><DIV><DIV><P STYLE="margin:0 0 11 0;"><SPAN STYLE="font-size:12pt">DSHS makes no representation as to the accuracy, adequacy, reliability, availability or completeness of the crash reports or the data collected from them and is not responsible for any errors or omissions in such records or data. Under no circumstance will DSHS have any liability for any loss or damage incurred by any party as a result of the use of the crash records or the data collected from them. Under 23 U.S. Code 148 and 23 U.S. Code 407, safety data, reports, surveys, schedules, list complied or collected for the purpose of identifying, evaluating, or planning the safety enhancement of potential crash sites, hazardous roadway conditions, or railway-highway crossings are not subject to discovery or admitted into evidence in a Federal or State court proceeding or considered for other purposes in any action for damages arising from any occurrence at a location mentioned or addressed in such report, surveys, schedules, lists, or data.</SPAN></P><P STYLE="margin:0 0 11 0;"><SPAN STYLE="font-size:12pt">The State of Delaware makes no warranty or representation, expressed or implied, with respect to the quality, content, accuracy, completeness, currency, or non-infringement of proprietary rights, of any of the GIS or other data or information, or any other materials and items, that are displayed or made available for download from this site. All such data, information, items and materials (collectively, the “FirstMap Data”) are provided "as is" and users are fully and solely responsible for any consequences of use. FirstMap Data may have been created from a variety of sources, including sources beyond the control of the State of Delaware, and are subject to change without notice. To the extent you use, apply, add to, modify or implement this information in your own information system or other setting, or otherwise for your own purposes, you do so at your own risk. In no event shall the State of Delaware or its agencies, officers, employees, agents, or representatives be liable for any damages of any kind or nature whatsoever including, but not limited to, direct, indirect, special, punitive, incidental, exemplary or consequential damages arising from your downloading, modifying, sharing, distributing, or using of FirstMap Data even if notified of the possibility of such damages. Further, the State of Delaware does not accept liability for any damages or misrepresentation caused by inaccuracies in the FirstMap Data or as a result of changes to the FirstMap Data, nor is there responsibility assumed to maintain the FirstMap Data in any manner or form. </SPAN></P></DIV></DIV></DIV>
crash
accident
public
Mark A. Prettyman
Delaware Department of Technology and Information
Software Engineer
801 Silver Lake Blvd
Dover
Delaware
19904
US
(302) 739-9500
Mark A. Prettyman
Mark A. Prettyman
Arshon Howard
Delaware Department of Safety & Homeland Security
Chief Community Relations
Arshon Howard
external
25522afbdc8b85262fdebdb555d89a0ce2a935b6
Mark A. Prettyman
Delaware Department of Technology and Information
Software Engineer
True
Mark A. Prettyman
Delaware Department of Safety and Homeland Security
Enterprise Geodatabase Feature Class
dataset
EPSG
6.18.3(9.3.1.2)
0
Simple
FALSE
0
TRUE
FALSE
TRN_CRASH_DATA
Feature Class
0
Data is to satisfy the requirements of 21 Del. C. § 313 to make de-identified crash data available to the public
21 Del. C. § 313
OBJECTID
OBJECTID
OID
4
10
0
Internal feature number.
Esri
Sequential unique whole numbers that are automatically generated.
CRASH_DATE
CRASH DATE
Date
8
0
0
The date on which the crash occurred.
FHWA (2012). "MMUCC Guideline - Model Minimum Uniform Crash Criteria," 4th Edition.
CRASH_TIME
CRASH TIME
String
8
0
0
The time at which the crash occurred.
FHWA (2012). "MMUCC Guideline - Model Minimum Uniform Crash Criteria," 4th Edition.
CRASH_DATETIME
CRASH DATE AND TIME
Date
8
0
0
The date and time at which the crash occurred.
FHWA (2012). "MMUCC Guideline - Model Minimum Uniform Crash Criteria," 4th Edition.
DAY_OF_WEEK
DAY OF WEEK CODE
String
2
0
0
Code to describe the day of week.
Code Text
01 Sunday
02 Monday
03 Tuesday
04 Wednesday
05 Thursday
06 Friday
07 Saturday
FHWA (2012). "MMUCC Guideline - Model Minimum Uniform Crash Criteria," 4th Edition.
DAY_OF_WEEK_DESC
DAY OF WEEK DESCRIPTION
String
18
0
0
Day of the week that the crash occurred.
FHWA (2012). "MMUCC Guideline - Model Minimum Uniform Crash Criteria," 4th Edition.
CRASH_CLASS
CRASH CLASSIFICATION CODE
String
4
0
0
Code to describe the ECRASH Report type crash classification.
Code Text
01 Non-Reportable
02 Property Damage Only
03 Personal Injury Crash
04 Fatality Crash
FHWA (2012). "MMUCC Guideline - Model Minimum Uniform Crash Criteria," 4th Edition.
CRASH_CLASS_DESC
CRASH CLASSIFICATION DESCRIPTION
String
42
0
0
ECRASH reports are sorted into four categories. The categories are determined by the following factors, which are applied in sequence: 1) the nature of the crash location (i.e., private property vs. trafficway); 2) the most serious level of injury (i.e., fatal involved, personal injury involved, or property damage only); and 3) if a property damage collision only, the apparent extent (dollar value estimate) of damage. Private property is defined here as location inputs of “outside of right of way (private property)” and “private parking lot” in the collision reports. See also 21 Del. C. § 101(55). Trafficways are excluded from private property.
A “Non-Reportable” classification occurs under two circumstances. First, all collisions on private property, regardless of whether the collision results in a fatality, personal injury, or property damage only, are included in this category. Second, all collisions on trafficways that result in property damage only (i.e., a non-fatal or non-personal injury event) and are of an apparent extent below $2,000 (or $1,500 if before September 30, 2021), which is Delaware’s duty to report a collision threshold. See generally 21 Del. C. § 4203.
A “Property Damage Only” classification refers to a collision that occurs on a trafficway and results in property damage only (i.e., a non-fatal or non-personal injury event) to an apparent extent of $2,000 or more (or $1,500 or more if before September 30, 2021). A “Personal Injury Crash” or “Fatality Crash” classification refers to a collision that occurs on a trafficway and the category reflects the most serious degree of injury present.
FHWA (2012). "MMUCC Guideline - Model Minimum Uniform Crash Criteria," 4th Edition.
PRIV_PROP_COLL
COLLISION ON PRIVATE PROPERTY
String
2
0
0
Private property is defined here as location inputs of “outside of right of way (private property)” and “private parking lot” in the collision reports. See also 21 Del. C. §101(55). Trafficways are excluded from private property.
This field can be used in conjunction with the “Crash Classification” field to determine if a “Non-Reportable” report involved a “Property Damage Only” collision on a trafficway that resulted in an apparent extent (dollar value estimate) of damage below the statutory reporting threshold.
Text
No
Yes
FHWA (2012). "MMUCC Guideline - Model Minimum Uniform Crash Criteria," 4th Edition.
PED_INVOLVED
PEDESTRIAN INVOLVED
String
2
0
0
Indicates if a pedestrian was involved in the collision.
FHWA (2012). "MMUCC Guideline - Model Minimum Uniform Crash Criteria," 4th Edition.
IMPACT
MANNER OF IMPACT CODE
String
4
0
0
Code to describe the manner of impact.
Code Text
01 Front to rear
02 Front to front
03 Angle
04 Sideswipe, same direction
05 Sideswipe, opposite direction
06 Rear to side
07 Rear to rear
88 Other
99 Unknown
00 Not a collision between two vehicles
FHWA (2012). "MMUCC Guideline - Model Minimum Uniform Crash Criteria," 4th Edition.
IMPACT_DESC
MANNER OF IMPACT DESCRIPTION
String
72
0
0
Where the first harmful event involves a collision between two motor vehicles in transport, the manner of impact identifies how the two motor vehicles initially came together, without regard to the direction of force. Motor vehicles not in transport (e.g., parked and working motor vehicles, like short term stationary utility work (repairing electric, gas, or water lines within the trafficway)) are not included.
FHWA (2012). "MMUCC Guideline - Model Minimum Uniform Crash Criteria," 4th Edition.
ALCOHOL_INVOLVED
ALCOHOL INVOLVED
String
2
0
0
Indicates suspected alcohol use by "any person” involved in the crash, excluding passengers. "Any person" could include a driver, pedestrian, bicyclist/cyclist, occupant of a non-motor vehicle, an unknown type of non-motorist, or a reporting person for a hit and run, regardless of if that person was at fault or which vehicle, if any, they occupied.
Text
No
Yes
FHWA (2012). "MMUCC Guideline - Model Minimum Uniform Crash Criteria," 4th Edition.
DRUG_INVOLVED
DRUG INVOLVED
String
2
0
0
Indicates suspected drug use by "any person” involved in the crash, excluding passengers. "Any person" could include a driver, pedestrian, bicyclist/cyclist, occupant of a non-motor vehicle, an unknown type of non-motorist, or a reporting person for a hit and run, regardless of if that person was at fault or which vehicle, if any, they occupied.
Text
No
Yes
FHWA (2012). "MMUCC Guideline - Model Minimum Uniform Crash Criteria," 4th Edition.
ROAD_SURFACE
ROAD SURFACE CODE
String
4
0
0
Code to describe the road surface condition.
Code Text
01 Dry
02 Wet
03 Snow
04 Ice/Frost
05 Sand
06 Water (standing, moving)
07 Slush
08 Oil
09 Mud, Dirt, Gravel
88 Other
99 Unknown
FHWA (2012). "MMUCC Guideline - Model Minimum Uniform Crash Criteria," 4th Edition.
ROAD_SURFACE_DESC
ROAD SURFACE DESCRIPTION
String
48
0
0
The prevailing apparent condition of the road at the time of the crash.
FHWA (2012). "MMUCC Guideline - Model Minimum Uniform Crash Criteria," 4th Edition.
LIGHT_COND
LIGHTING CONDITION CODE
String
4
0
0
Code to describe the ambient lighting condition.
Code Text
01 Daylight
02 Dawn
03 Dusk
04 Dark-Lighted
05 Dark-Not Lighted
06 Dark-Unknown Lighting
88 Other
99 Unknown
FHWA (2012). "MMUCC Guideline - Model Minimum Uniform Crash Criteria," 4th Edition.
LIGHT_COND_DESC
LIGHTING CONDITION DESCRIPTION
String
42
0
0
The type/level of ambient light that existed at the time of the crash.
FHWA (2012). "MMUCC Guideline - Model Minimum Uniform Crash Criteria," 4th Edition.
WEATHER_1
WEATHER 1 CODE
String
4
0
0
Code to describe the primary weather condition.
Code Text
01 Clear
02 Cloudy
03 Fog, Smog, Smoke
04 Rain
05 Sleet, Hail (freezing rain or drizzle)
06 Snow
07 Blowing Snow
08 Severe Crosswinds
09 Blowing Sand, Soil, Dirt
88 Other
99 Unknown
FHWA (2012). "MMUCC Guideline - Model Minimum Uniform Crash Criteria," 4th Edition.
WEATHER_1_DESC
WEATHER 1 DESCRIPTION
String
76
0
0
The prevailing atmospheric condition that existed at the time of the crash.
FHWA (2012). "MMUCC Guideline - Model Minimum Uniform Crash Criteria," 4th Edition.
WEATHER_2
WEATHER 2 CODE
String
4
0
0
Code to describe the secondary weather condition.
Code Text
01 Clear
02 Cloudy
03 Fog, Smog, Smoke
04 Rain
05 Sleet, Hail (freezing rain or drizzle)
06 Snow
07 Blowing Snow
08 Severe Crosswinds
09 Blowing Sand, Soil, Dirt
88 Other
99 Unknown
FHWA (2012). "MMUCC Guideline - Model Minimum Uniform Crash Criteria," 4th Edition.
WEATHER_2_DESC
WEATHER 2 DESCRIPTION
String
76
0
0
The secondary atmospheric condition that existed at the time of the crash, if reported.
FHWA (2012). "MMUCC Guideline - Model Minimum Uniform Crash Criteria," 4th Edition.
SEATBELT_USED
SEATBELT USED
String
2
0
0
Indicates if seatbelts are used by all occupants (i.e., drivers and passengers in aggregate) required to do so in all vehicles involved in the collision. A “Yes” response indicates all occupants were compliant. A “No” response indicates that one or more individuals in the collision was not using the required occupant protection system.
Text
No
Yes
FHWA (2012). "MMUCC Guideline - Model Minimum Uniform Crash Criteria," 4th Edition.
MC_INVOLVED
MOTORCYCLE INVOLVED
String
2
0
0
FHWA (2012). "MMUCC Guideline - Model Minimum Uniform Crash Criteria," 4th Edition.
Indicates whether a motorcycle or scooter was involved in the crash. This field is included to provide context to the “Motorcycle Helmet Used” field.
Text
No
Yes
MC_HELMET_USED
MOTORCYCLE HELMET USED
String
2
0
0
FHWA (2012). "MMUCC Guideline - Model Minimum Uniform Crash Criteria," 4th Edition.
Indicates whether a helmet was used by any person involved in a crash that involved either a motorcycle or a scooter. For example, a collision involving two passenger sedans (i.e., a vehicle type with no helmet requirements) will populate a value of “No.” This field is to be used in conjunction with the “Motorcycle Involved” field to filter the results to collisions that involve a motorcycle or scooter.
Text
No
Yes
BIKE_INVOLVED
BICYCLED INVOLVED
String
2
0
0
FHWA (2012). "MMUCC Guideline - Model Minimum Uniform Crash Criteria," 4th Edition.
Indicates whether a bicycle (i.e., two-wheel, non-motorized cycle) or other cycle (i.e., non-motorized pedal-powered vehicle other than a bicycle, such as a unicycle or adult tricycle) was involved in the crash. The “Bicycle Involved” field populates by aggregating if any non-motorist is designated a “bicyclist” or “other cyclist.” Text
No
Yes
BIKE_HELMET_USED
BICYCLE HELMET USED
String
2
0
0
FHWA (2012). "MMUCC Guideline - Model Minimum Uniform Crash Criteria," 4th Edition.
Indicates if a non-motorist bicyclist or other cyclist has “Helmet” listed in the safety equipment field of the Person table of ECRASH.
Text
No
Yes
LATITUDE
LATITUDE
Double
8
38
8
FHWA (2012). "MMUCC Guideline - Model Minimum Uniform Crash Criteria," 4th Edition.
The geographic latitude of the crash, given in decimal degrees.
LONGITUDE
LONGITUDE
Double
8
38
8
FHWA (2012). "MMUCC Guideline - Model Minimum Uniform Crash Criteria," 4th Edition.
The geographic longitude of the crash, given in decimal degrees.
PRI_CONTRIB_CIRCUM
PRIMARY CONTRIBUTING CIRCUMSTANCES CODE
String
4
0
0
FHWA (2012). "MMUCC Guideline - Model Minimum Uniform Crash Criteria," 4th Edition.
Code to describe the primary contributing circumstance.
Code Text
01 Speeding
02 Failed to yield right of way
03 Passed Stop Sign
04 Disregard Traffic Signal
05 Wrong side or wrong way
06 Improper passing
07 Improper lane change
08 Following too close
09 Made improper turn
10 Driving under the influence
11 Driver inattention, distraction, or fatigue
12 Driving in a careless or reckless manner
13 Driving in an aggressive manner
14 Improper backing
15 Other improper driving
16 Mechanical defects
17 Animal in Roadway - Deer
18 Animal in Roadway - Other Animal
19 Other environmental circumstances - weather, glare, visibility obstructed, etc.
20 Roadway circumstances - debris, holes, work zone, etc.
21 Pedestrian
88 Other
99 Unknown
PRI_CONTRIB_CIRCUM_DESC
PRIMARY CONTRIBUTING CIRCUMSTANCES DESCRIPTION
String
100
0
0
FHWA (2012). "MMUCC Guideline - Model Minimum Uniform Crash Criteria," 4th Edition.
Primary circumstance that may have contributed to the crash.
SCHOOL_BUS_INVOLVED
SCHOOL BUS INVOLVED CODE
String
4
0
0
FHWA (2012). "MMUCC Guideline - Model Minimum Uniform Crash Criteria," 4th Edition.
Code to describe if a school bus is involved in a crash.
Code Text
00 No
01 Yes, School Bus Directly Involved
02 Yes, School Bus Indirectly Involved
SCHOOL_BUS_INVOLVED_DESC
SCHOOL BUS INVOLVED DESCRIPTION
String
48
0
0
FHWA (2012). "MMUCC Guideline - Model Minimum Uniform Crash Criteria," 4th Edition.
Indicates whether a school bus or motor vehicle functioning as a school bus for a school-related purpose is involved in the crash.
WORK_ZONE
WORK ZONE
String
2
0
0
FHWA (2012). "MMUCC Guideline - Model Minimum Uniform Crash Criteria," 4th Edition.
Specifies if the crash is in a construction, maintenance, or utility work zone or if it related to activity within a work zone.
Text
No
Yes
WORK_ZONE_LOCATION
WORK ZONE LOCATION CODE
String
4
0
0
FHWA (2012). "MMUCC Guideline - Model Minimum Uniform Crash Criteria," 4th Edition.
Code to describe the work zone location.
Code Text
01 Before the First Work Zone Warning Sign
02 Advance Warning Area
03 Transition Area
04 Activity Area
05 Termination Area
WORK_ZONE_LOCATION_DESC
WORK ZONE LOCATION DESCRIPTION
String
78
0
0
FHWA (2012). "MMUCC Guideline - Model Minimum Uniform Crash Criteria," 4th Edition.
Specifies the section of the work zone (which extends from the first warning sign, signal or flashing lights to the “End Road Work” sign or the last traffic control device pertinent for that work activity) in which the crash occurs.
WORK_ZONE_TYPE
WORK ZONE TYPE CODE
String
4
0
0
FHWA (2012). "MMUCC Guideline - Model Minimum Uniform Crash Criteria," 4th Edition.
Code to describe the work zone type.
Code Text
01 Lane Closure
02 Lane Shift/Crossover
03 Work on Shoulder or Median
04 Intermittent or Moving Work
88 Other
WORK_ZONE_TYPE_DESC
WORK ZONE TYPE DESCRIPTION
String
54
0
0
FHWA (2012). "MMUCC Guideline - Model Minimum Uniform Crash Criteria," 4th Edition.
Specifies the type of work zone in which the crash occurs.
WORKERS_PRESENT
WORKERS PRESENT
String
2
0
0
FHWA (2012). "MMUCC Guideline - Model Minimum Uniform Crash Criteria," 4th Edition.
Specifies if workers were present in the work zone at the time of the crash.
Code Text
01 No
02 Yes
09 Unknown
SHAPE
SHAPE
Geometry
8
0
0
Feature geometry.
Esri
Coordinates defining the features.
COUNTY
COUNTY CODE
Code used to define the county.
Code Text
K Kent
N New Castle
S Sussex
FHWA (2012). "MMUCC Guideline - Model Minimum Uniform Crash Criteria," 4th Edition.
String
2
0
0
COUNTY_DESC
COUNTY NAME
The name of the county in which the crash occurred.
FHWA (2012). "MMUCC Guideline - Model Minimum Uniform Crash Criteria," 4th Edition.
String
20
0
0
YEAR
YEAR
The year in which the crash occured.
FHWA (2012). "MMUCC Guideline - Model Minimum Uniform Crash Criteria," 4th Edition.
Integer
20250618
Mark A. Prettyman
Delaware Department of Technology and Information
Software Engineer
801 Silver Lake Blvd
Dover
Delaware
19904
US
(302) 739-9500
Mark A. Prettyman
Arshon Howard
Delaware Department of Safety & Homeland Security
Chief Community Relations
Arshon Howard
303 Transportation Cir
Dover
DE
19901
US
(302) 744-2680