WELL · 42-097-31442 · DISTRICT 9

M. Bayer #22

Plugged

Cooke County · Cooke County Regular field  · Vertical

M. Bayer #22 (API 42-097-31442) is a plugged well in Cooke County, plugged May 19, 2023, last operated by Petro Invest Energy Services LLC.

The RRC has issued one drilling permit, issued September 13, 1979, permitted to 1,990 ft.

It was permitted by Powell & Brown and has since transferred to Petro Invest Energy Services LLC on the wellbore schedule.

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

Operator of record

Petro Invest Energy Services LLC

Permitted by Powell & Brown; the EWA schedule now lists a different operator.

Hallandale, FL · P-5 Y, filed Oct 7, 2022 · (954) 454-7676

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulePetro Invest Energy Services LLC
Production reportsPetro Invest Energy Services,llcthrough Oct 2015
Latest permitPowell & BrownSep 13, 1979

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

1,990
total depth, ft
1
permits on file
Sep 13, 1979
last permit issued
May 1, 1980
completed
2.42K
cumulative oil, bbl
82
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
May 1, 1980
Shut in
—
Plugged
May 19, 2023

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

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
M. Bayer O-13-30695Cooke County RegularPetro Invest Energy Services,llc311.51K15Dec 2006 – Jul 2026
Luke, F. L. -B- Lease O-13-9664Cooke County RegularDSB Energy, LLC890367Jan 1993 – Mar 2007

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. 1Powell & BrownJan 1993 → Dec 1994
  2. 2Hacker Brothers Oil Company, IncJan 1995 → Feb 1998
  3. 3Seelye, William L.Jun 2004 → Sep 2005
  4. 4DSB Energy, LLCFeb 2006 → Dec 2011
  5. 5Petro Invest Energy Services,llcAug 2014 → Oct 2015

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
57864-99DrillPowell & BrownSep 13, 1979Sep 13, 1979—1,990

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-13-9664————
—— O-13-30695————

Perforations

Perforated and open-hole intervals.

FromToType
1,1581,165Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
2.3751,160——
4.51,3257.875425 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
00Dec 8, 2006May 16, 1980—
00Jan 12, 1984May 16, 1980—

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