Mapped connections
Access
No published information is currently available for this location.
Richmond Pharmaceuticals Inc.
3510 Mayland Court, Henrico, VA 23233
Free facility risk profile
Location Snapshot
Richmond Pharmaceuticals Inc. · 3510 Mayland Court, Henrico, VA 23233
Source-linked transport, power, flood, and wildfire context for the mapped location.
Utility-system measure
Power outages
No published information is currently available for this location.
Area context
Flood
- Modeled events per year
- 0.96
- Published events
- 27
- Impacted area
- 68.6 sq mi
FEMA NRI county-level modeled flood context; it does not describe this facility's flood zone or predict a facility loss.
- Geography
- county modeled planning context
- Method
- exact_county_fips
- Source date
- December 2025 (1.20.0)
- Retrieved
- 2026-08-01T00:20:00+00:00
- What this does not establish
- This product uses the Federal Emergency Management Agency’s National Risk Index dataset API or downloadable datasets but is not endorsed by FEMA. The Federal Government or FEMA cannot vouch for the data or analyses derived from these data after the data have been retrieved from the Agency's website(s).
Modeled area context
Wildfire
No published information is currently available for this location.
Pro facility evidence
Detailed evidence is protected
Compliance records, source evidence, climate context, and hazard visuals are available after the server verifies an active Pro entitlement.
Unlock facility visualsCharts, gauges, comparisons, and source evidence after Pro verification. No protected facts are shown here.
Match under review. Some source records for this facility are still being checked; current confidence is review.
Transport access
Context · not part of the assessment
Distance from this facility’s reviewed coordinate to the nearest official freight destinations. By-road is the shortest drivable route on the public road network for a car profile — not a truck route.
| Class | Destination | Straight-line mi | By road mi | Drive |
|---|---|---|---|---|
| Seaport · USACE statistical area | Virginia, VA, Port ofCoastal · USACE rank 9 · 68,766,562 short tons total | 85 | 105 | 2 h 21 min |
| Seaport · USACE statistical area | Baltimore, MDCoastal · USACE rank 14 · 49,875,915 short tons total | 132 | 163 | 3 h 27 min |
| Marine terminal · dock-level point | Port of Virginia · Richmond Marine Terminal (RMT)Virginia Port Authority · CSX, NS | 15 | 18 | 28 min |
| Marine terminal · dock-level point | Port of Virginia · Newport News Marine Terminal (NNMT)Virginia Port Authority · CSX | 78 | 90 | 1 h 47 min |
| Rail intermodal | Richmond Marine Termianl (RMT)CSX, NS · TOFC/COFC · Port of Virginia | 15 | 18 | 28 min |
| Rail intermodal | Norfolk International Terminals (NIT)CSX, NS via NPBL · COFC · Port of Virginia | 85 | 101 | 2 h 9 min |
| Rail intermodal | Virginia International Gateway (VIG)CSX, NS via CWRY · COFC · Port of Virginia | 85 | 103 | 2 h 4 min |
| Air cargo | RICHMOND INTL (RIC)1 air-to-truck facility · Federal Express · vintage 09/2018 | 16 | 19 | 30 min |
| Air cargo | WASHINGTON DULLES INTL (IAD)5 air-to-truck facilities · American Airlines; Lufthansa Cargo; United Air Lines; Southwest Airlines; Worldwide Flight Services; Federal Express … · vintage 12/2018 | 92 | 111 | 2 h 27 min |
Sources: U.S. DOT Bureau of Transportation Statistics, National Transportation Atlas Database (Principal Ports, Intermodal Freight Facilities Rail TOFC/COFC, Air-to-Truck, Marine Ro-Ro), public domain. By-road routing © OpenStreetMap contributors (ODbL), routing by OSRM; shortest drivable route, not HOS, permit, weight, or hazmat aware. USACE principal-port polygons are tonnage-statistics areas, not dock footprints; the marine-terminal row is the dock-level point. Air-to-truck facilities reflect the dataset’s stated vintage. Straight-line and by-road figures describe proximity to an official source feature only; they do not establish route access, legal ingress, gate hours, truck restrictions, service, capacity, or that this facility uses any listed destination.
Request a profile correction
Provide a source link and explain what should be reviewed, including operator changes, closures, or a requested removal. Requests are moderated and never change or remove a profile automatically.