WELL · 42-363-35080 · DISTRICT 7

Deaton Laverne #3

Y

Palo Pinto County · Hart Ranch (Strawn 2850) field · Temp Abandoned  · Vertical

Deaton Laverne #3 (API 42-363-35080) is a well in Palo Pinto County operated by Robert C. Brower LLC, completed April 30, 2002 and listed as temp abandoned on the RRC schedule.

The RRC has issued one drilling permit (amended once), issued March 25, 2002, permitted to 3,400 ft.

It was permitted by Lexus Gas Corporation and has since transferred to Robert C. Brower LLC on the wellbore schedule.

Completion filings report one formation top, including Strawn.

No lease production has been reported under this well’s leases.

Operator of record

Robert C. Brower LLC

Permitted by Lexus Gas Corporation; the EWA schedule now lists a different operator.

Southlake, TX · P-5 Y, filed Jan 4, 2026 · (580) 554-5555

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleRobert C. Brower LLC
Production reportsStonebriar Oil LLCthrough Sep 2023
Latest permitLexus Gas CorporationMar 25, 2002

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

3,400
total depth, ft
2
permits on file
Mar 25, 2002
last permit issued
Apr 30, 2002
completed
0
cumulative oil, bbl
219K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Apr 2002 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Apr 30, 2002
Shut in
—
Plugged
—

Operator's P-5 on the schedule: X

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; this well is the only one on it.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Deaton, Laverne G-8-189088Hart Ranch (Strawn 2850)Robert C. Brower, LLC10219KApr 2002 – Jul 2026

Gas, mcf lease total

Last 12 months 0 · prior 12 0

0100200202420252026

Chain of custody

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

  1. 1Lexus Gas CorporationMay 2002 → Jul 2003
  2. 2Sky Resources, Inc.Aug 2003 → Jul 2023
  3. 3Stonebriar Oil LLCAug 2023 → Sep 2023

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
518514-98DrillLexus Gas CorporationApr 1, 2002Mar 25, 2002Apr 3, 20023,400
518514-99DrillLexus Gas CorporationMar 25, 2002Mar 25, 2002—2,999

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-8-189088————

Formation tops

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

FormationMD ftSubsea
Strawn2,460-1,512

Perforations

Perforated and open-hole intervals.

FromToType
2,7662,722Perforated
2,8262,830Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62528012.5200 S
4.53,1257.875570 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
00Aug 21, 2002Jun 17, 2002Yes
00Jun 27, 2002——

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