TEXAS · WELLS · PARKER COUNTY · BENNETT LEASE · API 42-367-33483 · DISTRICT 6E

Bennett #1

Y

Parker County · Brazos East (Caddo) field · Producing  · Vertical

Bennett #1 (API 42-367-33483) is a well in Parker County operated by J-Tec Operating LLC, completed April 5, 2004 and listed as producing on the RRC schedule.

The RRC has issued 2 drilling permits between 2003 and 2006, permitted to 4,458 ft.

It was permitted by Telesis Operating CO., Inc. and has since transferred to J-Tec Operating LLC on the wellbore schedule.

No lease production has been reported under this well’s leases.

Operator of record

J-Tec Operating LLC

Permitted by Telesis Operating Co., Inc.; the EWA schedule now lists a different operator.

Based in
Mineral Wells, TX
P-5 status
Active (A)
P-5 last filed
May 6, 2026
Phone
(940) 654-5114

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulenone
Production reportsJ-Tec Production, LLCthrough Apr 2026
Latest permitTelesis Operating Co., Inc.Jul 25, 2006
4,458
total depth, ft
2
permits on file
Jul 25, 2006
last permit issued
Apr 5, 2004
completed
0
cumulative oil, bbl
179K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Apr 2004 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Apr 5, 2004
Shut in
—
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.

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 →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Bennett G-8-203528Brazos, East (Caddo)J-Tec Operating, LLC10179KApr 2004 – Jul 2026

Gas, mcf lease total

Last 12 months 4,450 · prior 12 5,458(-18%)

05001K202420252026

Chain of custody

Every operator that reported production on this well's lease, in order.

  1. 1Telesis Operating Co., Inc.Apr 2004 → Jul 2008
  2. 2Vantage Fort Worth Energy LLCAug 2008 → Jan 2013
  3. 3Borderline Operating Corp.Feb 2013 → Aug 2015
  4. 4Tower Resources IncSep 2015 → Nov 2016
  5. 5Box Hill Operating, Inc.Dec 2016 → Nov 2017
  6. 6Attis Operating Inc.Dec 2017 → Mar 2020
  7. 7J-Tec Production, LLCApr 2020 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
623002-99Field transferTelesis Operating Co., Inc.Jul 21, 2006Jul 25, 2006—4,999
540129-99DrillTelesis Operating Co., Inc.Dec 23, 2003Dec 23, 2003Feb 27, 20044,999

Completions

CompletedLeaseFieldOperatorStatusDepth
Apr 5, 2004Bennett G-8-203528Brazos East (Caddo)J-Tec Operating LLCProducing4,458

Perforations

Perforated and open-hole intervals.

FromToType
4,1884,198Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62525412.25160 S
4.54,4657.875215 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
00Apr 25, 2007Jul 28, 2006—
00Nov 8, 2004Sep 1, 2004Yes
00Sep 30, 2004——

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.

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