WELL · 42-469-33154 · DISTRICT 2
Musselman #6
Victoria County · Salem (1170) field · Vertical
Musselman #6 (API 42-469-33154) is a plugged well in Victoria County, plugged October 21, 1997, last operated by Patterson Petroleum Inc..
The RRC has issued one drilling permit (amended once), issued May 8, 1996, permitted to 2,300 ft.
Completion filings report one formation top, including Miocene (undifferentiated).
Operator of record
Snyder, TX · P-5 Y, filed Jul 7, 2000 · 436 permits on file
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Patterson Petroleum Inc. |
| Production reports | Patterson Petroleum, Inc.through Apr 1997 |
| Latest permit | Patterson Petroleum, Inc.May 8, 1996 |
- 2,300
- total depth, ft
- 2
- permits on file
- May 8, 1996
- last permit issued
- May 22, 1996
- completed
- 0
- cumulative oil, bbl
- 20.3K
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · May 1996 THROUGH Oct 1997
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- May 22, 1996
- Shut in
- —
- Plugged
- Oct 21, 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 →
| Lease | Field | Reporting operator | Wells | Oil, bbl | Gas, mcf | Reported |
|---|---|---|---|---|---|---|
| Musselman G-2-158943 | Salem (1170) | Patterson Petroleum, Inc. | 1 | 0 | 20.3K | May 1996 – Oct 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.
- 1Patterson Petroleum, Inc.Oct 1996 → Apr 1997
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 447914-98 | Drill | Patterson Petroleum, Inc. | Jun 17, 1996 | May 8, 1996 | May 10, 1996 | 2,300 |
| 447914-99 | Drill | Patterson Petroleum, Inc. | May 8, 1996 | May 8, 1996 | — | 2,300 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — G-2-158943 | — | — | — | — |
Formation tops
As filed on W-2/G-1. Subsea from 90 ft elevation.Download CSV →
| Formation | MD ft | Subsea |
|---|---|---|
| Miocene (undifferentiated)MIOCENE | 1,234 | -1,144 |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 1,286 | 1,292 | Perforated |
| 1,716 | 1,724 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 8.625 | 253 | 12.25 | 170 S |
| 2.875 | 1,855 | 7.875 | 372 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 | Jul 29, 1996 | Jun 19, 1996 | Yes |
| 00 | Jul 16, 1996 | — | — |
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-469-33154 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-469-33154 → 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/46933154, documented in the API reference.