WELL · 42-339-30557 · DISTRICT 3

M & M Minerals #1

Plugged

Montgomery County · Indian Hills North (G Sand) field  · Vertical

M & M Minerals #1 (API 42-339-30557) is a plugged well in Montgomery County, plugged May 19, 1997, last operated by O Sand Production Inc..

The RRC has issued 2 drilling permits between 1982 and 1983, permitted to 7,000 ft.

It was permitted by Texas Louisiana Petroleum CO. and has since transferred to O Sand Production Inc. on the wellbore schedule.

Completion filings report 2 formation tops, including Cockfield, (G Sand).

Its lease has reported 8.19K barrels of oil and 42.6K mcf of gas since January 1993, last reporting in July 1997.

Operator of record

O Sand Production Inc.

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

Tomball, TX · P-5 Y, filed Sep 6, 2002

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleO Sand Production Inc.
Production reportsO'Sand Production, Inc.through Oct 1996
Latest permitTexas Louisiana Petroleum Co.Oct 13, 1983

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

7,000
total depth, ft
2
permits on file
Oct 13, 1983
last permit issued
Oct 23, 1983
completed
8.19K
cumulative oil, bbl
42.6K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 1997

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Oct 23, 1983
Shut in
—
Plugged
May 19, 1997

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
M & M Minerals O-3-17249Indian Hills, North (G Sand)O'Sand Production, Inc.18.19K42.6KJan 1993 – Jul 1997

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. 1O'Sand Production, Inc.Jan 1993 → Oct 1996

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
217054-99RecompletionTexas Louisiana Petroleum Co.Sep 29, 1983Oct 13, 1983—5,905
181833-99DrillTexas Louisiana Petroleum Co.Dec 30, 1982Dec 30, 1982—7,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-3-17249————

Formation tops

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

FormationMD ftSubsea
Cockfield5,448-5,246
(G Sand)5,732-5,530

Perforations

Perforated and open-hole intervals.

FromToType
5,4485,450Perforated
5,7325,734Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62551212.25140 S
2.3755,413—435 S
4.56,0317.25140 S
4.56,089—140 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 24, 1984Jan 17, 1984—
00Feb 7, 1984Jan 17, 1984—
00Jan 12, 1984Jul 25, 1983—

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