WELL · 42-413-31684 · DISTRICT 7

Meador 15 #1

Plugged

Schleicher County · Velrex (Henderson Upper) field  · Vertical

Meador 15 #1 (API 42-413-31684) is a plugged well in Schleicher County, plugged March 21, 2011, last operated by Capitol Well Servicing CO. Inc..

The RRC has issued one drilling permit (amended once), issued August 18, 1988, permitted to 6,600 ft.

It was permitted by Questa Oil & Gas CO. and has since transferred to Capitol Well Servicing CO. Inc. on the wellbore schedule.

Completion filings report 4 formation tops, including San Angelo, Clear Fork, Wolfcamp, Canyon.

Operator of record

Capitol Well Servicing Co. Inc.

Permitted by Questa Oil & Gas Co.; the EWA schedule now lists a different operator.

Oklahoma City, OK · P-5 Y, filed Aug 5, 2022 · 15 permits on file · (405) 677-0359

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleCapitol Well Servicing Co. Inc.
Production reportsCapitol Well Servicing Co., Inc.through Nov 2010
Latest permitQuesta Oil & Gas Co.Aug 18, 1988

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

6,600
total depth, ft
2
permits on file
Aug 18, 1988
last permit issued
Dec 24, 1988
completed
0
cumulative oil, bbl
98.1K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Mar 2011

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Dec 24, 1988
Shut in
—
Plugged
Mar 21, 2011

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
Meador "15" G-9-129488Velrex (Henderson Upper)Capitol Well Servicing Co., Inc.1098.1KJan 1993 – Mar 2011

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. 1Swift Energy CompanyJan 1993 → Jan 1998
  2. 2Capitol Well Servicing Co., Inc.May 1998 → Nov 2010

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
350253-98DrillQuesta Oil & Gas Co.Sep 19, 1988Aug 18, 1988—6,600
350253-99DrillQuesta Oil & Gas Co.Aug 17, 1988Aug 18, 1988—6,600

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-9-129488————

Formation tops

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

FormationMD ftSubsea
San Angelo1,0021,350
Clear ForkCLEARFORK1,904448
Wolfcamp4,047-1,695
Canyon6,285-3,933

Perforations

Perforated and open-hole intervals.

FromToType
6,1906,200Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62572311270 S
4.56,3647.875400 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 9, 1989Jan 12, 1989Yes
00Feb 8, 1989——

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