WELL · 42-009-41683 · DISTRICT 9
JDL Ranch #4603S
Archer County · Archer County Regular field · Vertical
Jdl Ranch #4603S (API 42-009-41683) is a plugged well in Archer County, plugged February 26, 2021, last operated by Jdl Operating LLC.
The RRC has issued one drilling permit, issued August 30, 2007, permitted to 1,500 ft.
Completion filings report 2 formation tops, including Gunsite Lm., Gunsite Sd..
Its lease has reported 23.6K barrels of oil since August 2007, last reporting in July 2026. The lease carries 4 wells, so these are lease totals, not this well alone.
Operator of record
Holliday, TX · P-5 Y, filed Nov 4, 2025 · 48 permits on file · (940) 691-1344
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | JDL Operating LLC |
| Production reports | JDL Operating, LLCthrough Apr 2026 |
| Latest permit | JDL Operating, LLCAug 30, 2007 |
- 1,500
- total depth, ft
- 1
- permits on file
- Aug 30, 2007
- last permit issued
- Dec 3, 2007
- completed
- 23.6K
- cumulative oil, bbl
- 0
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Aug 2007 THROUGH Jul 2026
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- Dec 3, 2007
- Shut in
- —
- Plugged
- Feb 26, 2021
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; they carry 4 wells in total, so volumes are shared.Why →
| Lease | Field | Reporting operator | Wells | Oil, bbl | Gas, mcf | Reported |
|---|---|---|---|---|---|---|
| JDL Ranch O-13-30846 | Archer County Regular | JDL Operating, LLC | 4 | 23.6K | 0 | Aug 2007 – Jul 2026 |
Oil, barrels lease total
Last 12 months 162 · prior 12 295(-45%)
Chain of custody
Every operator that reported production on this well's lease, in order.
- 1JDL Operating, LLCAug 2007 → Apr 2026
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 645253-99 | Drill | JDL Operating, LLC | Aug 29, 2007 | Aug 30, 2007 | Sep 4, 2007 | 1,500 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — O-13-30846 | — | — | — | — |
Formation tops
As filed on W-2/G-1. Subsea from 961 ft elevation.Download CSV →
| Formation | MD ft | Subsea |
|---|---|---|
| Gunsite Lm. | 1,176 | -215 |
| Gunsite Sd. | 1,198 | -237 |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 1,198 | 1,199 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 4.5 | 1,349 | 7.875 | 250 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 | Feb 25, 2008 | Dec 19, 2007 | Yes |
| 00 | Feb 13, 2008 | — | — |
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-009-41683 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-009-41683 → 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/00941683, documented in the API reference.