WELL · 42-487-32586 · DISTRICT 9

Lane #1

N

Wilbarger County · Main field  · Vertical

Lane #1 (API 42-487-32586) is a well in Wilbarger County operated by Dry Fork Production CO. LLC, completed April 10, 2006.

The RRC has issued 2 drilling permits between 2006 and 2017, permitted to 4,200 ft.

Completion filings report 3 formation tops, including Gunsight, Gunsite Lime, Canyon.

Its 2 leases have reported 33.1K barrels of oil since April 2006, last reporting in July 2026. The leases carry 3 wells, so these are lease totals, not this well alone.

Operator of record

Dry Fork Production Co. LLC

Wichita Falls, TX · P-5 Y, filed Feb 4, 2026 · 207 permits on file · (940) 704-7200

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleDry Fork Production Co. LLC
Production reportsJM Well Service, Inc.through Apr 2026
Latest permitDry Fork Production Co., LLCAug 31, 2017

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

4,200
total depth, ft
2
permits on file
Aug 31, 2017
last permit issued
Apr 10, 2006
completed
33.1K
cumulative oil, bbl
0
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Apr 2006 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Apr 10, 2006
Shut in
—
Plugged
—

Surface location

34.059356, -99.260885

OpenStreetMap → ·  Google Maps →

Permit surface location from the RRC GIS record, in Wilbarger County.

Lease production

PDQ LEASE REPORTS · REPORTED THROUGH APR 2026

Texas reports oil by lease, not by well. These are the 2 leases this well is completed on; they carry 3 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Lane O-13-33642Wilbarger County RegularJM Well Service, Inc.29.01K0Mar 2016 – Jul 2026
Lane O-13-30608MainDry Fork Production Co., LLC124.1K0Apr 2006 – Apr 2018

Oil, barrels lease total

Last 12 months 515 · prior 12 597(-14%)

050100150202420252026

Chain of custody

Every operator that reported production on this well's lease, in order.

  1. 1Dry Fork Production Co., LLCApr 2006 → Oct 2024
  2. 2JM Well Service, Inc.Nov 2024 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
830294-99Field transferDry Fork Production Co., LLCAug 24, 2017Aug 31, 2017Mar 15, 20064,200
615724-99DrillDry Fork Production Co., LLCMar 13, 2006Mar 13, 2006Mar 14, 20064,200

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-13-30608————
—— O-13-33642————

Formation tops

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

FormationMD ftSubsea
GunsightGUNSIGHT LIME2,600-1,339
Gunsite Lime2,600-1,339
CanyonCANYON SAND3,086-1,825
CanyonCANYON LIME3,170-1,909

Perforations

Perforated and open-hole intervals.

FromToType
3,0863,090Perforated
3,1723,192Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62511911.575 S
8.62511912.2575 S
4.53,3687.875200 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
00Jan 11, 2018Sep 6, 2017—
00Jul 28, 2014Jul 2, 2014—
00Sep 15, 2006Apr 18, 2006Yes
00May 17, 2006——

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.

Nearby wells and their tops

NEAREST 8 LOCATED WELLS WITH TOPS · WITHIN 16 KM

Draw a cross-section

This well's tops beside its 5 nearest neighbours, subsea-aligned so they line up regardless of surface terrain.

Open the cross-section →

Waggoner L42-487-33148

2.4 KM · Dry Fork Production Co., LLC · Section with this well →

Milham Sand2,670-1,429
Cisco2,921-1,680
Canyon3,193-1,952
King—
Coleman Junction—
Dyson Sand—
KMA—
Palo Pinto—

10 TOPS · FIRST 8

Waggoner L42-487-33167

2.8 KM · Dry Fork Production Co., LLC · Section with this well →

Gunsight2,640-1,414
Castlebury2,710-1,484
Noble Lime2,766-1,540
Milham Lime2,800-1,574
Sloan Sand2,850-1,624
Cisco—
Dyson Sand—
King—

10 TOPS · FIRST 8

Waggoner L42-487-33187

2.9 KM · Dry Fork Production Co., LLC · Section with this well →

Dyson Sand2,085-860
Milham Sand2,850-1,625
Caddo—
Strawn—
Palo Pinto—
KMA—
King—
Coleman Junction—

10 TOPS · FIRST 8

Waggoner L42-487-33207

3.0 KM · Dry Fork Production Co., LLC · Section with this well →

Castlbury Sand2,637-1,415
Canyon—
Cisco—
Coleman Junction—
Dyson Sand—
King—
KMA—
Milham Sand—

10 TOPS · FIRST 8

Stephens -B-42-487-33248

3.1 KM · Double E Oil & Gas, L. P. · Section with this well →

Milham Sand1,948-703
Canyon2,361-1,116
Palo Pinto—
KMA—
Caddo—
Dyson Sand—
Coleman Junction—
Cisco—

10 TOPS · FIRST 8

Walker Smith42-487-33161

3.3 KM · Dry Fork Production Co., LLC · Section with this well →

Coleman Junction800406
King1,570-364
Gunsight2,250-1,044
Dyson Sand—
KMA—
Strawn—
Cisco—
Canyon—

10 TOPS · FIRST 8

Humble-Stephens42-487-33235

3.4 KM · Double E Oil & Gas, L. P. · Section with this well →

Milham Sand2,000-742
Canyon2,356-1,098
Strawn—
Palo Pinto—
Caddo—
Cisco—
Coleman Junction—
Dyson Sand—

10 TOPS · FIRST 8

Humble-Stephens42-487-33249

3.6 KM · Double E Oil & Gas, L. P. · Section with this well →

Cisco1,259-1
Milham Sand2,059-801
Canyon2,358-1,100
Palo Pinto—
Caddo—
Strawn—
Coleman Junction—
Dyson Sand—

10 TOPS · FIRST 8

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/48732586, documented in the API reference.