WELL · 42-103-34216 · DISTRICT 8

Meister 22-1 #1

Plugged

Crane County · Tucker (Glorieta) field  · Vertical

Meister 22-1 #1 (API 42-103-34216) is a plugged well in Crane County, plugged July 11, 2018, last operated by Petroplex Energy Inc..

The RRC has issued 2 drilling permits (amended once) between 1993 and 2002, permitted to 6,000 ft.

Completion filings report 4 formation tops, including San Andres, Holt, Tubb, Simpson.

Its 2 leases have reported 46 barrels of oil and 117K mcf of gas since July 1996, last reporting in July 2018. The leases carry 2 wells, so these are lease totals, not this well alone.

Operator of record

Petroplex Energy Inc.

Midland, TX · P-5 Y, filed May 4, 2026 · 182 permits on file · (432) 687-2222

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulePetroplex Energy Inc.
Production reportsPetroplex Energy Inc.through Jan 2016
Latest permitPetroplex Energy Inc.Mar 26, 2002
6,000
total depth, ft
3
permits on file
Mar 26, 2002
last permit issued
Jul 15, 1996
completed
46
cumulative oil, bbl
117K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jul 1996 THROUGH Jul 2018

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Jul 15, 1996
Shut in
—
Plugged
Jul 11, 2018

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

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Meister 22 G-10-187960McKee (Wolfcamp)Petroplex Energy Inc.10117KSep 2001 – Jul 2018
Meister 22-1 O-10-35039Tucker (Glorieta)Petroplex Energy Inc.14628Jul 1996 – Jul 2002

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. 1Smith, John A.Jul 1996 → Feb 1998
  2. 2Petroplex Energy Inc.Sep 2001 → Jan 2016

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
518105-99RecompletionPetroplex Energy Inc.Mar 6, 2002Mar 26, 2002Sep 18, 20016,000
411854-98DrillSmith, John A.Aug 19, 1996May 20, 1993—6,000
411854-99DrillW.O.G., Inc.May 17, 1993May 20, 1993May 22, 19936,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-10-187960————
—— O-10-35039————

Formation tops

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

FormationMD ftSubsea
San Andres2,519-105
Holt3,502-1,088
Tubb3,925-1,511
Simpson5,214-2,800

Perforations

Perforated and open-hole intervals.

FromToType
2,5322,544Perforated
5,2215,259Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62552212.25325 S
5.56,0007.8751,100 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
00Oct 2, 2002Jun 27, 2002—
00Sep 27, 2002Feb 8, 2002Yes
00Apr 11, 2002——
00Oct 3, 1996Jul 23, 1996—
00Sep 11, 1996—Yes

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) and the University Lands library. 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/10334216, documented in the API reference.