TEXAS · WELLS · HARRIS COUNTY · JACINTOPORT LEASE · API 42-201-32619 · DISTRICT 03

Jacintoport #1

Shut in

Harris County · Yellow Rose (Yegua Y-2) field · Temp Abandoned  · Directional

Jacintoport #1 (API 42-201-32619) is a well in Harris County operated by Ballard Exploration Company Inc., completed April 11, 2001 and listed as temp abandoned on the RRC schedule, shut in August 1, 2006.

The RRC has issued one drilling permit (amended once), issued February 23, 2001, permitted to 12,355 ft.

Completion filings report 3 formation tops, including Frio, Vicksburg, Top Vegua.

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

Operator of record

Ballard Exploration Company Inc.

Based in
Houston, TX
P-5 status
Active (A)
P-5 last filed
Mar 4, 2026
Permits on file
464
Phone
(713) 651-0181

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleBallard Exploration Company Inc.
Production reportsBallard Exploration Company,inc.through Jul 2006
Latest permitBallard Exploration Company,inc.Feb 23, 2001
12,355
total depth, ft
2
permits on file
Feb 23, 2001
last permit issued
Apr 11, 2001
completed
0
cumulative oil, bbl
2.46M
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Apr 2001 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Apr 11, 2001
Shut in
Aug 1, 2006
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
Jacintoport G-3-184018Yellow Rose (Yegua Y-2)Ballard Exploration Company,inc.102.46MApr 2001 – Jul 2026

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

Chain of custody

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

  1. 1Ballard Exploration Company,inc.Apr 2001 → Jul 2006

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
505770-98DrillBallard Exploration Company,inc.Jul 27, 2001Feb 23, 2001—12,355
505770-99DrillBallard Exploration Company,inc.Feb 23, 2001Feb 23, 2001Feb 24, 200111,500

Completions

CompletedLeaseFieldOperatorStatusDepth
Apr 11, 2001Jacintoport G-3-184018Yellow Rose (Yegua Y-2)Ballard Exploration Company Inc.Temp Abandoned · shut in Aug 1, 200612,355

Formation tops

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

FormationMD ftSubsea
FrioTOP FRIO5,270-5,255
VicksburgTOP VICKSBURG7,980-7,965
Top Vegua10,900-10,885

Perforations

Perforated and open-hole intervals.

FromToType
10,59010,624Perforated
11,69211,732Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
13.3753,45317.5—
78,8059.625—
9.6259,11112.25—

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 19, 2001Aug 1, 2001Yes
00Sep 4, 2001——

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