WELL · 42-297-31701 · DISTRICT 2

Tullis #2

N

Live Oak County  · Vertical

Tullis #2 (API 42-297-31701) is a former disposal or injection well in Live Oak County, last operated by Carl, W. E.; its UIC permit is no longer active.

The RRC has issued 3 drilling permits between 1978 and 1988, permitted to 4,000 ft.

Completion filings report 5 formation tops, including Frio, Upper Cole, Hockley "A", Pettis.

Operator of record

Carl, W. E.

Corpus Chrsti, TX · P-5 Y, filed Dec 15, 1988 · 18 permits on file

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulenone
Production reportsnone
Latest permitCarl, W. E.Aug 23, 1988
4,000
total depth, ft
3
permits on file
Aug 23, 1988
last permit issued
—
completed
0
cumulative oil, bbl
0
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jun 2015

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
—
Shut in
—
Plugged
—

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 2 leases this well is completed on; they carry 3 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Tullis G-2-76383Tom Lyne NE. (Hockley)Awp Operating Company100Jan 1993 – Jun 2015
Tullis O-2-5650Tom Lyne, NE. (Hockley D)Awp Operating Company200Jan 1993 – Aug 2010

No volumes reported on these leases in the last three years.

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
350267-99RecompletionCarl, W. E.Aug 18, 1988Aug 23, 1988—3,826
36288-99OtherHamon, Jake L.Nov 6, 1978Nov 6, 1978—3,826
19448-99DrillHamon, Jake L.Mar 6, 1978Mar 6, 1978—4,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-2-76383————
—— O-2-5650————
—— O-2-5650————

Formation tops

As filed on W-2/G-1. Subsea from 275 ft elevation.Download CSV →

FormationMD ftSubsea
FrioFRIO VICKSBURG1274
FrioFRIO-VICKSBURG1274
Upper Cole2,230-1,955
Hockley "A"2,910-2,635
Pettis3,670-3,395
Pettus3,670-3,395

Perforations

Perforated and open-hole intervals.

FromToType
2,5442,564Perforated
3,0233,028Perforated
3,2203,223Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62581812.25330 S
2.3753,156——
4.53,8227.875575 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 →

SuffixFiledW-2 / G-1 dateLogs referenced
00Sep 16, 2010Mar 17, 2000—
00Apr 28, 2006Aug 22, 2005—
00Apr 3, 2006Aug 22, 2005—
00May 12, 2000Apr 10, 2000—
00Apr 10, 2000Nov 2, 1978—
00Jan 12, 1984Nov 2, 1978—
00Jan 12, 1984Apr 13, 1978—

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.

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

335K
bbl, last 12 reported months
6.32M
bbl, all reported
Feb 2016
reported through
UICKindStatusPermitted bbl/dMax psiZone ft
000089644W-14 DisposalPlugged Jun 27, 20162,0001,2652,530–2,620

MONTHLY INJECTED, BBL · H-10 · LAST 24 REPORTED MONTHS

Last 12 months 335,079 · prior 12 333,694(+0%)

010K20K30K20152016

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/29731701, documented in the API reference.