TEXAS · WELLS · WILLACY COUNTY · API 42-489-00210 · DISTRICT 04
Sauz Ranch Mulatos Pasture #120
Willacy County · Willamar West (Miocene 6300) field · Vertical
Sauz Ranch Mulatos Pasture #120 (API 42-489-00210) is a plugged well in Willacy County, plugged January 19, 1989, last operated by Exxon Corp..
The RRC has issued 2 drilling permits between 1981 and 1987, permitted to 8,000 ft.
Operator of record
- Based in
- Houston, TX
- P-5 status
- See remarks (S)
- P-5 last filed
- Mar 15, 1999
- Permits on file
- 19,549
- Phone
- (713) 431-1125
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Exxon Corp. |
| Production reports | none |
| Latest permit | Exxon Corp.Jan 22, 1987 |
- 8,000
- total depth, ft
- 2
- permits on file
- Jan 22, 1987
- last permit issued
- May 26, 1987
- completed
- —
- cumulative oil, bbl
- —
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- May 26, 1987
- Shut in
- —
- Plugged
- Jan 19, 1989
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.
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 325629-99 | Recompletion | Exxon Corp. | Jan 20, 1987 | Jan 22, 1987 | — | 8,000 |
| 116121-99 | Other | Exxon Corp. | Apr 27, 1981 | Apr 27, 1981 | — | 8,000 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| May 26, 1987 | Sauz Ranch Mulatos Pasture O-4-9032 | Willamar West (Miocene 6300) | Exxon Corp. | Plugged | — |
| Jun 23, 1981 | Sauz Ranch Mulatos Pasture O-4-9808 | Willamar West (Miocene 5300) | Parker & Parsley Development L.P | Plugged | — |
| Dec 22, 1964 | Sauz Ranch Mulatos Pasture O-4-3390 | Willamar West | Chestnut Explor. and Prod. Inc. | Plugged | — |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 5,088 | 5,095 | Perforated |
| 6,323 | 6,332 | Perforated |
| — | 6,332 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 9.625 | 1,531 | 12.25 | 625 S |
| 9.625 | 1,531 | — | — |
| 5.5 | 7,989 | 8.625 | 585 S |
| 5.5 | 7,989 | — | — |
| 2.375 | 8,106 | 7.875 | 100 S |
| 2.375 | 8,106 | — | — |
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 8, 1987 | Jun 12, 1987 | Yes |
| 00 | Jan 12, 1984 | Jul 22, 1981 | — |
| 00 | Jan 12, 1984 | Jul 15, 1966 | — |
| 00 | Jan 12, 1984 | — | — |
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-489-00210 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-489-00210 → 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.
Beyond the permit record
RRC UIC permits · H-10 reported volumes
Injection
- 0
- bbl, last 12 reported months
- 0
- bbl, all reported
- —
- reported through
| UIC | Kind | Status | Permitted bbl/d | Max psi | Zone ft |
|---|---|---|---|---|---|
| 000004759 | UIC Permit | Plugged Feb 10, 1989 | 0 | 0 | 3,226–0 |
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/48900210, documented in the API reference.