TEXAS · WELLS · WEBB COUNTY · SOUTH CALLAGHAN RANCH LEASE · API 42-479-35688 · DISTRICT 04
South Callaghan Ranch #109
Webb County · Benavides (Lobo Cons.) field · Producing · Vertical
- Fields on the latest permit · any of 3
- Contempo (Lobo) · Contempo (Lobo 1) · Contempo (Lobo 2)
- Not one formation; the well must be completed in one of them, and no target formation is stated.
South Callaghan Ranch #109 (API 42-479-35688) is a well in Webb County operated by Aldine Oil And Gas LP, completed April 8, 1993 and listed as producing on the RRC schedule, shut in March 1, 2014.
The RRC has issued one drilling permit (amended once), issued November 17, 1992, permitted to 9,197 ft.
It was permitted by Mobil Producing TX. & N.M. Inc. and has since transferred to Aldine Oil And Gas LP on the wellbore schedule.
Completion filings report 2 formation tops, including Lobo 3, Lobo 6.
Its lease has reported 218 barrels of oil and 1.07M mcf of gas since April 1993, with no volume in the three years through April 2026.
Operator of record
Permitted by Mobil Producing TX. & N.M. Inc.; the EWA schedule now lists a different operator.
- Based in
- Tomball, TX
- P-5 status
- Delinquent (D)
- P-5 last filed
- Jun 4, 2025
- Phone
- (281) 822-1400
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Aldine Oil and Gas LP |
| Production reports | Aldine Oil and Gas, LPthrough Feb 2014 |
| Latest permit | Mobil Producing TX. & N.M. Inc.Nov 17, 1992 |
The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.
- 9,197
- total depth, ft
- 2
- permits on file
- Nov 17, 1992
- last permit issued
- Apr 8, 1993
- completed
- 218
- cumulative oil, bbl
- 1.07M
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · APR 1993 THROUGH FEB 2014
Regulatory status · RRC wellbore file
- Schedule
- ON SCHEDULE
- Completed
- Apr 8, 1993
- Shut in
- Mar 1, 2014
- Plugged
- —
Operator's P-5 on the schedule: Active (A)
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.
Wells nearby
Every well with a location on file around this well, in any state, nearest first.
Texas locations come from drilling permits, so most older Texas wells have none and are not listed.
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 |
|---|---|---|---|---|---|---|
| South Callaghan Ranch G-4-144946 | Benavides (Lobo Cons.) | Aldine Oil and Gas, LP | 1 | 218 | 1.07M | Apr 1993 – Feb 2014 |
No volumes reported on these leases in the last three years.
Wells named South Callaghan Ranch
Aldine Oil and Gas LP's other wells filed under this lease name in Webb County, newest permit first. The RRC gives a gas well its own lease number, so the name is what joins the wells of a unit.
Loading the lease's wellsChain of custody
Every operator that reported production on this well's lease, in order.
- 1Mobil Producing TX. & N.M. Inc.Apr 1993 → Apr 1998
- 2Michael Petroleum CorporationMay 1998 → Dec 2001
- 3Calpine Natural Gas CompanyJan 2002 → Apr 2002
- 4Calpine Natural Gas Company L.P.May 2002 → Jul 2002
- 5Calpine Natural Gas L.P.Aug 2002 → Dec 2005
- 6Rosetta Resources Operating LPJan 2006 → Mar 2012
- 7Pinpoint Energy Operating, LLCApr 2012 → Aug 2012
- 8Petropoint Energy Operating, LLCSep 2012 → Feb 2014
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 406183-98 | Drill | Mobil Producing TX. & N.M. Inc. | Dec 16, 1992 | Nov 17, 1992 | Dec 29, 1992 | 9,500 |
| 406183-99 | Drill | Mobil Producing TX. & N.M. Inc. | Nov 17, 1992 | Nov 17, 1992 | — | 9,500 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| Apr 8, 1993 | South Callaghan Ranch G-4-144946 | Benavides (Lobo Cons.) | Aldine Oil and Gas LP | Producing · shut in Mar 1, 2014 | 9,197 |
Formation tops
As filed on W-2/G-1. Subsea from 598 ft elevation.Download CSV →
| Formation | MD ft | Subsea |
|---|---|---|
| Lobo 3 | 8,485 | -7,887 |
| Lobo 6 | 8,760 | -8,162 |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 7,982 | 8,124 | Perforated |
| 8,255 | 8,265 | Perforated |
| 8,788 | 8,892 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 9.625 | 275 | 12.25 | 200 S |
| 7 | 6,817 | 8.75 | 325 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. The record date is the RRC's own date on the record, not the day the report was filed: 462,034 of the state's filings carry 1984-01-12. About these reports →
| Suffix | RRC record date | W-2 / G-1 date | Logs referenced |
|---|---|---|---|
| 00 | May 7, 1993 | Apr 20, 1993 | Yes |
| 00 | May 3, 1993 | — | — |
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-479-35688 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-479-35688 → scanned completion filings
Log images filed since 2004 open from the RRC's log search for this well; none are loaded here for it.
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/47935688, documented in the API reference.