WELL · 42-079-32066 · DISTRICT 8

Slaughter George M #1

Y

Cochran County · Levelland field · Producing  · Vertical

Slaughter George M #1 (API 42-079-32066) is a well in Cochran County operated by Atlas Operating LLC, completed December 10, 1984 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued November 21, 1984, permitted to 4,850 ft.

It was permitted by Reata Energy Corporation and has since transferred to Atlas Operating LLC on the wellbore schedule.

Completion filings report one formation top, including San Andres.

Its lease has reported 30.8K barrels of oil and 402 mcf of gas since January 1993, last reporting in July 2026.

Operator of record

Atlas Operating LLC

Permitted by Reata Energy Corporation; the EWA schedule now lists a different operator.

Houston, TX · P-5 Y, filed Oct 4, 2025 · 78 permits on file · (281) 893-9400

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleAtlas Operating LLC
Production reportsAtlas Operating LLCthrough Mar 2026
Latest permitReata Energy CorporationNov 21, 1984

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

4,850
total depth, ft
1
permits on file
Nov 21, 1984
last permit issued
Dec 10, 1984
completed
30.8K
cumulative oil, bbl
402
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Dec 10, 1984
Shut in
—
Plugged
—

Operator's P-5 on the schedule: H

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
Slaughter, George M O-11-65198LevellandAtlas Operating LLC130.8K402Jan 1993 – Jul 2026

Oil, barrels lease total

Last 12 months 398 · prior 12 752(-47%)

050100150202420252026

Chain of custody

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

  1. 1B & B Operating Co, Inc.Jan 1993 → Sep 2002
  2. 2Slape Oil Company, Inc.Oct 2002 → Jun 2011
  3. 3Crossroads Energy Partners, LLCJul 2011 → Mar 2018
  4. 4Atlas Operating LLCApr 2018 → Mar 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
258486-99DrillReata Energy CorporationNov 21, 1984Nov 21, 1984Nov 25, 19844,850

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-11-65198————

Formation tops

As filed on W-2/G-1. Download CSV →

FormationMD ft
San Andres3,820

Perforations

Perforated and open-hole intervals.

FromToType
4,7604,795Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62545512.25300 S
4.54,8187.8751,700 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
00Feb 22, 1985Feb 1, 1985—
00Feb 20, 1985——

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