WELL · 42-149-32786 · DISTRICT 3

Donella #1HR

Plugged

Fayette County · Giddings (Austin Chalk-3) field  · Horizontal

Donella #1HR (API 42-149-32786) is a plugged horizontal well in Fayette County, plugged August 1, 2014, last operated by Evolution Operating CO. Inc..

The RRC has issued 2 drilling permits between 1993 and 2007, permitted to 12,500 ft.

Completion filings report 6 formation tops, including Midway, Navarro, Olmos, Pecan Gap.

Its lease has reported 58.3K barrels of oil and 438K mcf of gas since October 1993, last reporting in July 2026. The lease carries 2 wells, so these are lease totals, not this well alone.

Operator of record

Evolution Operating Co. Inc.

Based in
Houston, TX
P-5 status
Inactive (I)
P-5 last filed
Jul 12, 2021
Permits on file
43
Phone
(713) 935-0122

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleEvolution Operating Co. Inc.
Production reportsEvolution Operating Co., Inc.through Feb 2013
Latest permitEvolution Operating Co., Inc.Nov 8, 2007
12,500
total depth, ft
2
permits on file
Nov 8, 2007
last permit issued
Mar 13, 2008
completed
58.3K
cumulative oil, bbl
438K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Oct 1993 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Mar 13, 2008
Shut in
—
Plugged
Aug 1, 2014

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

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Donella O-3-22195Giddings (Austin Chalk-3)Evolution Operating Co., Inc.258.3K438KOct 1993 – Jul 2026

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. 1Chesapeake Operating, Inc.Oct 1993 → May 2005
  2. 2Evolution Operating Co., Inc.Mar 2008 → Aug 2010

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
647507-99RecompletionEvolution Operating Co., Inc.Oct 10, 2007Nov 8, 2007Nov 16, 200712,500
413964-99DrillChesapeake Operating, Inc.Jul 16, 1993Jul 16, 1993Aug 2, 199311,400

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-3-22195————
—— O-3-22195————

Formation tops

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

FormationMD ftSubsea
Midway7,605-7,272
Navarro8,642-8,309
Olmos9,162-8,829
Pecan Gap10,079-9,746
Austin Chalk10,540-10,207
Lower Chalk11,139-10,806

Perforations

Perforated and open-hole intervals.

FromToType
10,58412,473Perforated
10,58414,287Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
10.753,45114.752,010 S
7.62510,5849.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. About these reports →

SuffixFiledW-2 / G-1 dateLogs referenced
00Jan 14, 2009May 9, 2008—
00Dec 9, 2008——
00Nov 23, 1993Oct 20, 1993Yes
00Nov 18, 1993——

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