WELL · 42-367-30412 · DISTRICT 7
Leatherman #1
Parker County · Vertical
Leatherman #1 (API 42-367-30412) is a permitted well in Parker County filed by Dallas Production, Inc.; no completion report is on file yet.
The RRC has issued 2 drilling permits between 1980 and 1982, permitted to 4,979 ft.
Operator of record
- Based in
- Dallas, TX
- P-5 status
- Inactive (I)
- P-5 last filed
- Feb 11, 2020
- Permits on file
- 823
- Phone
- (214) 369-9266
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | none |
| Production reports | Somerset Operating, LLCthrough Feb 2026 |
| Latest permit | Dallas Production, Inc.Aug 4, 1982 |
- 4,979
- total depth, ft
- 2
- permits on file
- Aug 4, 1982
- last permit issued
- —
- completed
- 0
- cumulative oil, bbl
- 720K
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2026
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- —
- Shut in
- —
- Plugged
- —
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 →
| Lease | Field | Reporting operator | Wells | Oil, bbl | Gas, mcf | Reported |
|---|---|---|---|---|---|---|
| Leatherman G-8-101306 | Bethesda (Big Saline) | Somerset Operating, LLC | 1 | 0 | 720K | Jan 1993 – Jul 2026 |
Gas, mcf lease total
Last 12 months 17,882 · prior 12 25,309(-29%)
Chain of custody
Every operator that reported production on this well's lease, in order.
- 1Dallas Production, Inc.Jan 1993 → Sep 2005
- 2Shell Western E&POct 2005 → Dec 2007
- 3Pioneer Natural Res. USA, Inc.Jan 2008 → Nov 2010
- 4MKS Natural Gas CompanyDec 2010 → Jan 2012
- 5OxxnFeb 2012 → Aug 2023
- 6Somerset Operating, LLCSep 2023 → Feb 2026
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 168198-99 | Recompletion | Dallas Production, Inc. | Aug 4, 1982 | Aug 4, 1982 | — | 4,979 |
| 102032-99 | Drill | Dallas Production, Inc. | Dec 12, 1980 | Dec 12, 1980 | Aug 24, 1976 | 4,979 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — G-8-101306 | — | — | — | — |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 2,762 | 2,828 | Perforated |
| 4,820 | 4,825 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 8.625 | 307 | 12.25 | 210 S |
| 2.375 | 2,740 | — | — |
| 4.5 | 2,948 | 7.875 | 260 S |
| 2.875 | 4,820 | 7.875 | 295 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 →
| Suffix | Filed | W-2 / G-1 date | Logs referenced |
|---|---|---|---|
| 00 | Jan 12, 1984 | Jul 23, 1982 | — |
| 00 | Jan 12, 1984 | Nov 24, 1980 | — |
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.
- Wellbore filings for 42-367-30412 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-367-30412 → scanned completion filings
Log images are in archives with no per-well link: the RRC's Neubus archive (2004 onward). then paste it into their search.
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/36730412, documented in the API reference.