WELL · 42-187-33637 · DISTRICT 1
Malone Chester #22
Guadalupe County · LA Vernia field · Producing · Vertical
Malone Chester #22 (API 42-187-33637) is a well in Guadalupe County operated by Malone Oil Production, completed November 14, 2016 and listed as producing on the RRC schedule.
The RRC has issued one drilling permit, issued September 24, 2014, permitted to 900 ft.
Completion filings report 8 formation tops, including Navarro, Austin Chalk, Buda, Catahoula.
Its lease has reported 19.8K barrels of oil and 21 mcf of gas since January 1993, last reporting in July 2026. The lease carries 22 wells, so these are lease totals, not this well alone.
Operator of record
LA Vernia, TX · P-5 Y, filed Apr 4, 2026 · 2 permits on file · (806) 570-7273
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Malone Oil Production |
| Production reports | Malone Oil Productionthrough Apr 2026 |
| Latest permit | Malone Oil ProductionSep 24, 2014 |
- 900
- total depth, ft
- 1
- permits on file
- Sep 24, 2014
- last permit issued
- Nov 14, 2016
- completed
- 19.8K
- cumulative oil, bbl
- 21
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2026
Regulatory status · RRC wellbore file
- Schedule
- ON SCHEDULE
- Completed
- Nov 14, 2016
- 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 22 wells in total, so volumes are shared.Why →
| Lease | Field | Reporting operator | Wells | Oil, bbl | Gas, mcf | Reported |
|---|---|---|---|---|---|---|
| Malone, Chester O-1-6205 | LA Vernia | Malone Oil Production | 22 | 19.8K | 21 | Jan 1993 – Jul 2026 |
Oil, barrels lease total
Last 12 months 288 · prior 12 282(+2%)
Chain of custody
Every operator that reported production on this well's lease, in order.
- 1Malone Oil ProductionJan 1993 → Apr 2026
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 795263-99 | Drill | Malone Oil Production | Aug 28, 2014 | Sep 24, 2014 | Sep 15, 2016 | 900 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — O-1-6205 | — | — | — | — |
Formation tops
As filed on W-2/G-1. Subsea from 470 ft elevation.Download CSV →
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 720 | 732 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 4.5 | 800 | 6.25 | 115 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 →
| Suffix | Filed | W-2 / G-1 date | Logs referenced |
|---|---|---|---|
| 00 | Jun 29, 2017 | May 17, 2017 | 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.
- Wellbore filings for 42-187-33637 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-187-33637 → scanned completion filings
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/18733637, documented in the API reference.