TEXAS · WELLS · ARCHER COUNTY · DAYTON LEASE · API 42-009-41897 · DISTRICT 7C

Dayton #2

Plugged

Archer County · Archer County Regular field  · Vertical

Dayton #2 (API 42-009-41897) is a plugged well in Archer County, plugged July 11, 2011, last operated by Dry Fork Production CO. LLC.

The RRC has issued one drilling permit, issued October 17, 2008, permitted to 1,400 ft.

Completion filings report one formation top, including Gunsight.

Its lease has reported 56 barrels of oil since January 2009, with no volume in the three years through April 2026. The lease carries 2 wells, so these are lease totals, not this well alone.

Operator of record

Dry Fork Production Co. LLC

Based in
Wichita Falls, TX
P-5 status
Active – Extension (X)
P-5 last filed
May 1, 2026
Permits on file
207
Phone
(940) 723-7052

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleDry Fork Production Co. LLC
Production reportsDry Fork Production Co., LLCthrough Feb 2010
Latest permitDry Fork Production Co., LLCOct 17, 2008
1,400
total depth, ft
1
permits on file
Oct 17, 2008
last permit issued
Jan 12, 2009
completed
56
cumulative oil, bbl
0
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Mar 2009 THROUGH Feb 2010

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Jan 12, 2009
Shut in
—
Plugged
Jul 11, 2011

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.

Wells nearby

Every well with a location on file around this well, in any state, nearest first.

Loading the map…

Open the full map →

Texas locations come from drilling permits, so most older Texas wells have none and are not listed.

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 2 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Dayton O-13-31370Archer County RegularDry Fork Production Co., LLC2560Jan 2009 – Feb 2010

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

Wells named Dayton

Dry Fork Production Co. LLC's other wells filed under this lease name in Archer County, newest permit first. The RRC gives a gas well its own lease number, so the name is what joins the wells of a unit.

Loading the lease's wells

Chain of custody

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

  1. 1Dry Fork Production Co., LLCMar 2009 → Feb 2010

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
671654-99DrillDry Fork Production Co., LLCSep 22, 2008Oct 17, 2008Dec 1, 20081,400

Completions

CompletedLeaseFieldOperatorStatusDepth
Jan 12, 2009Dayton O-13-31370Archer County RegularDry Fork Production Co. LLCPlugged—

Formation tops

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

FormationMD ftSubsea
GunsightGUNSIGHT LIME1,143-22

Perforations

Perforated and open-hole intervals.

FromToType
1,1451,148Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
4.51,2807.875300 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. The record date is the RRC's own date on the record, not the day the report was filed: 462,034 of the state's filings carry 1984-01-12. About these reports →

SuffixRRC record dateW-2 / G-1 dateLogs referenced
00Oct 1, 2009Mar 19, 2009—
00Sep 4, 2009——

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 filed since 2004 open from the RRC's log search for this well; none are loaded here for it.

Find logs withinmiles of this well:List →Map →

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