WELL · 42-025-33738 · DISTRICT 2
Sasser #4
Bee County · Heard Ranch (3900) field · Vertical
Sasser #4 (API 42-025-33738) is a plugged well in Bee County, plugged April 21, 2014, last operated by Mego Resources LLC.
The RRC has issued one drilling permit (amended once), issued August 18, 2010, permitted to 5,200 ft.
Completion filings report 3 formation tops, including Oakville, Catahula, Sinton.
Operator of record
Taft, TX · P-5 Y, filed Nov 4, 2025 · 67 permits on file · (361) 815-2158
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Mego Resources LLC |
| Production reports | Mego Resources, LLCthrough Mar 2014 |
| Latest permit | Mego Resources, LLCAug 18, 2010 |
- 5,200
- total depth, ft
- 2
- permits on file
- Aug 18, 2010
- last permit issued
- Mar 9, 2011
- completed
- 0
- cumulative oil, bbl
- 184K
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Nov 2010 THROUGH Apr 2014
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- Mar 9, 2011
- Shut in
- —
- Plugged
- Apr 21, 2014
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 |
|---|---|---|---|---|---|---|
| Sasser G-2-258905 | Wildcat | Mego Resources, LLC | 1 | 0 | 184K | Nov 2010 – Apr 2014 |
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.
- 1Mego Resources, LLCMar 2011 → Mar 2014
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 700754-98 | Drill | Mego Resources, LLC | Jul 15, 2011 | Aug 18, 2010 | Oct 1, 2010 | 5,200 |
| 700754-99 | Drill | Mego Resources, LLC | Aug 16, 2010 | Aug 18, 2010 | Oct 1, 2010 | 5,200 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — G-2-258905 | — | — | — | — |
Formation tops
As filed on W-2/G-1. Subsea from 153 ft elevation.Download CSV →
| Formation | MD ft | Subsea |
|---|---|---|
| Oakville | 1,900 | -1,747 |
| Catahula | 2,810 | -2,657 |
| Sinton | 3,970 | -3,817 |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 3,790 | 3,792 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 8.625 | 815 | 12.25 | 325 S |
| 4.5 | 5,150 | 7.875 | 1,013 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 27, 2012 | Mar 24, 2011 | — |
| 00 | Mar 28, 2011 | Nov 30, 2010 | Yes |
| 00 | Feb 16, 2011 | — | — |
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-025-33738 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-025-33738 → 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/02533738, documented in the API reference.