WELL · 42-203-32732 · DISTRICT 6
Massingale J. #7
Harrison County · Waskom (Travis Peak 1) field · Vertical
Massingale J. #7 (API 42-203-32732) is a plugged well in Harrison County, plugged December 5, 2022, last operated by Shelby Operating Company.
The RRC has issued one drilling permit, issued June 3, 2002, permitted to 6,550 ft.
Completion filings report 4 formation tops, including Fredricksburg, Anhydrite Top, Pettit, Travis Peak.
Operator of record
Dallas, TX · P-5 Y, filed Dec 4, 2025 · 86 permits on file · (214) 739-5384
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Shelby Operating Company |
| Production reports | Shelby Operating Companythrough Aug 2012 |
| Latest permit | Shelby Operating CompanyJun 3, 2002 |
- 6,550
- total depth, ft
- 1
- permits on file
- Jun 3, 2002
- last permit issued
- Oct 11, 2002
- completed
- 0
- cumulative oil, bbl
- 558K
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Oct 2002 THROUGH Dec 2022
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- Oct 11, 2002
- Shut in
- —
- Plugged
- Dec 5, 2022
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 →
| Lease | Field | Reporting operator | Wells | Oil, bbl | Gas, mcf | Reported |
|---|---|---|---|---|---|---|
| Massingale, J. G-6-191063 | Waskom (Travis Peak 1) | Shelby Operating Company | 1 | 0 | 558K | Oct 2002 – Dec 2022 |
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.
- 1Shelby Operating CompanyOct 2002 → Aug 2012
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 520552-99 | Drill | Shelby Operating Company | May 31, 2002 | Jun 3, 2002 | Jul 13, 2002 | 6,550 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — G-6-191063 | — | — | — | — |
Formation tops
As filed on W-2/G-1. Subsea from 260 ft elevation.Download CSV →
| Formation | MD ft | Subsea |
|---|---|---|
| Fredricksburg | 2,355 | -2,095 |
| Anhydrite Top | 4,480 | -4,220 |
| Pettit | 5,640 | -5,380 |
| Travis Peak | 5,872 | -5,612 |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 5,886 | 5,892 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 8.625 | 440 | 11 | 140 S |
| 5.5 | 6,550 | 7.875 | 755 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 | Nov 13, 2002 | Oct 17, 2002 | Yes |
| 00 | Oct 29, 2002 | — | — |
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-203-32732 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-203-32732 → 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/20332732, documented in the API reference.