WELL · 42-055-34580 · DISTRICT 1
Callihan M. W. -C- #1C
Caldwell County · Luling-Branyon field · Producing · Vertical
Callihan M. W. -C- #1C (API 42-055-34580) is a well in Caldwell County operated by Meb LLC, completed October 18, 1991 and listed as producing on the RRC schedule.
The RRC has issued one drilling permit, issued September 5, 1991, permitted to 2,350 ft.
It was permitted by Awm Oil and has since transferred to Meb LLC on the wellbore schedule.
Completion filings report 3 formation tops, including Austin Chalk, Eagle Ford, Buda.
Its lease has reported 8.79K barrels of oil and 5.87K mcf of gas since January 1993, last reporting in July 2026.
Operator of record
Permitted by Awm Oil; the EWA schedule now lists a different operator.
Austin, TX · P-5 Y, filed Jan 5, 2026 · 4 permits on file · (512) 290-8661
SOURCE · RRC EWA WELLBORE SCHEDULE
- 2,350
- total depth, ft
- 1
- permits on file
- Sep 5, 1991
- last permit issued
- Oct 18, 1991
- completed
- 8.79K
- cumulative oil, bbl
- 5.87K
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2026
Regulatory status · RRC wellbore file
- Schedule
- ON SCHEDULE
- Completed
- Oct 18, 1991
- Shut in
- —
- Plugged
- —
Operator's P-5 on the schedule: X
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 |
|---|---|---|---|---|---|---|
| Callihan, M. W. -C- O-1-13294 | Luling-Branyon | Meb, LLC | 1 | 8.79K | 5.87K | Jan 1993 – Jul 2026 |
Oil, barrels lease total
Last 12 months 121 · prior 12 81(+49%)
Chain of custody
Every operator that reported production on this well's lease, in order.
- 1Awm OilJan 1993 → Jan 1993
- 2LMN Oil and Gas, Inc.Feb 1993 → Feb 2001
- 3Pickett Oil Co.Mar 2001 → Aug 2007
- 4DJ Exploration, Inc.Nov 2007 → Nov 2017
- 5Meb, LLCDec 2017 → Apr 2026
Permits
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — O-1-13294 | — | — | — | — |
Formation tops
As filed on W-2/G-1. Subsea from 423 ft elevation.Download CSV →
| Formation | MD ft | Subsea |
|---|---|---|
| Austin Chalk | 1,850 | -1,427 |
| Eagle FordEAGLEFORD SHALE | 2,100 | -1,677 |
| Buda | 2,125 | -1,702 |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 1,868 | 2,096 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 4.5 | 2,150 | 7.875 | 423 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 | Nov 20, 1991 | Nov 6, 1991 | Yes |
| 00 | Nov 15, 1991 | — | — |
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-055-34580 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-055-34580 → 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/05534580, documented in the API reference.