WELL · 42-501-31967 · DISTRICT 8

Conditt #1

Y

Yoakum County · Prentice field · Producing  · Vertical

Conditt #1 (API 42-501-31967) is a well in Yoakum County operated by Beaver Oil & Gas Operating LLC, completed October 23, 1981 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued December 31, 1980, permitted to 6,800 ft.

It was permitted by Regency Petroleum CO. and has since transferred to Beaver Oil & Gas Operating LLC on the wellbore schedule.

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

Operator of record

Beaver Oil & Gas Operating LLC

Permitted by Regency Petroleum Co.; the EWA schedule now lists a different operator.

Austin, TX · P-5 Y, filed Apr 4, 2026 · (318) 469-3099

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleBeaver Oil & Gas Operating LLC
Production reportsBeaver Oil & Gas Operating, LLCthrough Apr 2026
Latest permitRegency Petroleum Co.Dec 31, 1980

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

6,800
total depth, ft
1
permits on file
Dec 31, 1980
last permit issued
Oct 23, 1981
completed
114K
cumulative oil, bbl
36.2K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Oct 23, 1981
Shut in
—
Plugged
—

Operator's P-5 on the schedule: Delinquent

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
Conditt O-11-63578PrenticeBeaver Oil & Gas Operating, LLC2114K36.2KJan 1993 – Jul 2026

Oil, barrels lease total

Last 12 months 1,216 · prior 12 1,235(-2%)

0100200202420252026

Chain of custody

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

  1. 1Regency Petroleum Co.Jan 1993 → Aug 2002
  2. 2Regency Petroleum Co. of New MexSep 2002 → Apr 2008
  3. 3Axis Energy CorporationMay 2008 → Oct 2012
  4. 4Fivestones Energy LLCNov 2012 → Jun 2022
  5. 5Beaver Oil & Gas Operating, LLCJul 2022 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
104909-99DrillRegency Petroleum Co.Dec 31, 1980Dec 31, 1980Jun 9, 19816,800

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-11-63578————

Perforations

Perforated and open-hole intervals.

FromToType
5,9365,950Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.6252,36512.251,050 S
2.3756,020——
4.56,4007.8751,000 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 12, 1984Nov 13, 1981—

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