WELL · 42-493-30216 · DISTRICT 1
Moy Sam #1
Wilson County · Mosser (Buda) field · Vertical
Moy Sam #1 (API 42-493-30216) is a plugged well in Wilson County, plugged August 9, 2008, last operated by Wainoco Halbouty Mitchell Energy.
The RRC has issued one drilling permit, issued April 10, 1979, permitted to 7,700 ft.
Its lease has reported 38.6K barrels of oil and 1.96K mcf of gas since January 1993, last reporting in December 2008.
Operator of record
Wainoco Halbouty Mitchell Energy
Houston, TX · P-5 Y, filed Oct 15, 1984 · 2 permits on file
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Wainoco Halbouty Mitchell Energy |
| Production reports | Bodden Productionthrough Nov 2006 |
| Latest permit | Wainoco Halbouty Mitchell EnergyApr 10, 1979 |
The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.
- 7,700
- total depth, ft
- 1
- permits on file
- Apr 10, 1979
- last permit issued
- —
- completed
- 38.6K
- cumulative oil, bbl
- 1.96K
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Dec 2008
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- —
- Shut in
- —
- Plugged
- Aug 9, 2008
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 |
|---|---|---|---|---|---|---|
| Moy, Sam O-1-5902 | Mosser (Austin Chalk) | Bodden Production | 1 | 38.6K | 1.96K | Jan 1993 – Dec 2008 |
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.
- 1Rec Well Service, Inc.Jan 1993 → Dec 1994
- 2Bodden ProductionJan 1995 → Nov 2006
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 46048-99 | Recompletion | Wainoco Halbouty Mitchell Energy | Apr 10, 1979 | Apr 10, 1979 | — | 7,700 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — O-1-5902 | — | — | — | — |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 7,569 | 7,606 | Perforated |
| 7,792 | — | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 8.625 | 729 | 12.25 | 400 S |
| — | 4,757 | 7.875 | — |
| 2.375 | 7,406 | — | — |
| 4.5 | 7,904 | 7.875 | — |
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 | Jan 12, 1984 | May 10, 1979 | — |
| 00 | Jan 12, 1984 | Jan 26, 1977 | — |
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-493-30216 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-493-30216 → 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/49330216, documented in the API reference.