WELL · 42-225-30829 · DISTRICT 6

Dailey Estate #1

Plugged

Houston County · Navarro Crossing (Dexter East) field  · Vertical

Dailey Estate #1 (API 42-225-30829) is a plugged well in Houston County, plugged September 29, 2006, last operated by Palmer Petroleum Inc..

The RRC has issued 2 drilling permits between 1991 and 2005, permitted to 6,500 ft.

Completion filings report 6 formation tops, including Midway, Pecan Gap, Austin Chalk, Woodbine.

Its 2 leases have reported 529 barrels of oil and 552K mcf of gas since January 1993, last reporting in July 2026. The leases carry 3 wells, so these are lease totals, not this well alone.

Operator of record

Palmer Petroleum Inc.

Shreveport, LA · P-5 Y, filed Jun 4, 2025 · 304 permits on file · (318) 222-0517

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulePalmer Petroleum Inc.
Production reportsPalmer Petroleum Inc.through May 2006
Latest permitPalmer Petroleum Inc.Jul 28, 2005
6,500
total depth, ft
2
permits on file
Jul 28, 2005
last permit issued
Jan 7, 1992
completed
529
cumulative oil, bbl
552K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Jan 7, 1992
Shut in
—
Plugged
Sep 29, 2006

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 2 leases this well is completed on; they carry 3 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Dailey Estate O-6-13182Navarro CrossingWeathers Exploration, Inc.2529132Mar 1993 – Jul 2026
Dailey Estate G-6-138196Navarro Crossing (Dexter, East)Palmer Petroleum Inc.10552KJan 1993 – Sep 2006

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

Chain of custody

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

  1. 1Palmer Petroleum Inc.Jan 1993 → May 2006

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
601494-99RecompletionPalmer Petroleum Inc.Jun 1, 2005Jul 28, 2005Feb 17, 20056,500
383332-99DrillPalmer Petroleum Inc.Jan 11, 1991Jan 15, 1991Mar 9, 19916,500

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-6-138196————
—— O-6-13182————

Formation tops

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

FormationMD ftSubsea
Midway2,666-2,437
Pecan Gap4,270-4,041
Austin Chalk5,290-5,061
Woodbine5,725-5,496
Dexter Fm.5,807-5,578
Dexter Sand5,927-5,698

Perforations

Perforated and open-hole intervals.

FromToType
5,8205,824Perforated
6,3766,379Perforated
6,3826,390Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.6251,31011375 S
4.56,5007.875790 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 25, 2007Apr 20, 2005Yes
00Oct 12, 2005——
00May 6, 1992Apr 10, 1992—
00Jun 13, 1991Apr 22, 1991Yes
00Jun 3, 1991—Yes

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.

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