WELL · 42-365-32795 · DISTRICT 6

Richardson SWD #2

WaterPlugged

Panola County · Carthage N. (Glen Rose 3760) field  · Vertical

Richardson Swd #2 (API 42-365-32795) is a plugged well in Panola County, plugged April 15, 1999, last operated by Hawk Gathering System Inc..

The RRC has issued one drilling permit, issued March 5, 1993, permitted to 6,200 ft.

It was permitted by Lacy, R., Inc. and has since transferred to Hawk Gathering System Inc. on the wellbore schedule.

Completion filings report 4 formation tops, including Glen Rose, BMA, Pettit, Travis Peak.

Operator of record

Hawk Gathering System Inc.

Permitted by Lacy, R., Inc.; the EWA schedule now lists a different operator.

Longview, TX · P-5 Y, filed Jul 8, 2005 · 1 permits on file

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleHawk Gathering System Inc.
Production reportsnone
Latest permitLacy, R., Inc.Mar 5, 1993

The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.

6,200
total depth, ft
1
permits on file
Mar 5, 1993
last permit issued
Jul 22, 1993
completed
0
cumulative oil, bbl
0
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jul 1993 THROUGH Apr 1999

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Jul 22, 1993
Shut in
—
Plugged
Apr 15, 1999

Surface location

No coordinates on the permit record yet. The RRC's GIS record usually lands within days of issuance; historical master-file permits never carry one.

Lease production

PDQ LEASE REPORTS · REPORTED THROUGH APR 2026

Texas reports oil by lease, not by well. These are the lease this well is completed on; this well is the only one on it.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Richardson SWD G-6-146178Carthage, N. (Glen Rose 3760)Hawk Gathering System, Inc.100Jul 1993 – Apr 1999

No volumes reported on these leases in the last three years.

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
409493-99DrillLacy, R., Inc.Mar 3, 1993Mar 5, 1993Jun 3, 19936,200

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-6-146178————

Formation tops

As filed on W-2/G-1. Subsea from 234 ft elevation.Download CSV →

FormationMD ftSubsea
Glen Rose3,354-3,120
BMA5,035-4,801
PettitUPPER PETTIT5,830-5,596
Travis Peak6,148-5,914

Perforations

Perforated and open-hole intervals.

FromToType
3,5863,592Perforated
3,8063,813Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.62540712.25225 S
5.56,4008.751,950 S

Completion filings

W-2 and G-1 reports on record in the RRC wellbore file, newest first. The suffix identifies the wellbore or completion event. About these reports →

SuffixFiledW-2 / G-1 dateLogs referenced
00Oct 7, 1993Aug 6, 1993—
00Aug 27, 1993——

The source documents

Petrora holds the structured record. The scanned filings live at the RRC; these links open its search already filled in for this API.

Log images are in archives with no per-well link: the RRC's Neubus archive (2004 onward). then paste it into their search.

Beyond the permit record

RRC UIC permits · H-10 reported volumes

Injection

195K
bbl, last 12 reported months
1.62M
bbl, all reported
Mar 1999
reported through
UICKindStatusPermitted bbl/dMax psiZone ft
000079859H-1 InjectionPlugged Apr 27, 19993,0001,7933,586–5,854

MONTHLY INJECTED, BBL · H-10 · LAST 24 REPORTED MONTHS

Last 12 months 195,028 · prior 12 273,091(-29%)

020K40K19981999

About this data

Permits from the RRC OGA049M master and daily daf420 files; wellbore and operator of record from the EWA schedule, weekly; completions, formation tops, casing, and perforations from the dbf900 wellbore file; production from PDQ lease reports, which lag two to three months; injection from UIC permits, H-10 reports, and TexNet daily volumes; earthquakes from the TexNet catalog.

New to these records? How to read a well page · API numbers · completion reports and tops · why production is by lease

Developers: this page as JSON is GET /v1/data/wells/36532795, documented in the API reference.