WELL · 42-239-32512 · DISTRICT 2

Sklar #1

Plugged

Jackson County · Simbrah (Halloween Yegua Sd.) field  · Vertical

Sklar #1 (API 42-239-32512) is a plugged well in Jackson County, plugged January 28, 1995, last operated by Swift Energy Company.

The RRC has issued 3 drilling permits between 1989 and 1994, permitted to 10,000 ft.

Completion filings report 3 formation tops, including Miocene (undifferentiated), Frio, Yegua.

Operator of record

Swift Energy Company

Based in
Houston, TX
P-5 status
Inactive (I)
P-5 last filed
Sep 22, 2005
Permits on file
719
Phone
(281) 874-2835

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleSwift Energy Company
Production reportsSwift Energy Companythrough Apr 1994
Latest permitSwift Energy CompanyJun 8, 1994
10,000
total depth, ft
3
permits on file
Jun 8, 1994
last permit issued
Oct 17, 1989
completed
0
cumulative oil, bbl
65.3K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jan 1995

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Oct 17, 1989
Shut in
—
Plugged
Jan 28, 1995

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

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Sklar G-2-150400Juan (Frio 5500)Swift Energy Company100May 1994 – Jan 1995
Sklar G-2-132989Simbrah (Halloween Yegua Sd.)Swift Energy Company10898Jan 1993 – Dec 1994
Sklar G-2-146995Miller (5700)Swift Energy Company1064.4KSep 1993 – Dec 1994

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. 1Swift Energy CompanyJan 1993 → Apr 1994

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
424429-99RecompletionSwift Energy CompanyMay 31, 1994Jun 8, 1994May 13, 19945,820
415324-99RecompletionSwift Energy CompanyAug 24, 1993Aug 24, 1993Sep 14, 19935,800
363403-99DrillTri-C Resources, Inc.Aug 31, 1989Sep 6, 1989Sep 24, 198910,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-2-132989————
—— G-2-146995————
—— G-2-150400————

Formation tops

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

FormationMD ftSubsea
Miocene (undifferentiated)MIOCENE1,000-984
Frio3,000-2,984
Yegua5,504-5,488
Yegua8,500-8,484

Perforations

Perforated and open-hole intervals.

FromToType
5,5045,510Perforated
5,6925,697Perforated
5,7025,709Perforated
9,0589,072Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
10.752,50014.751,335 S
7.6256,4159.875366 S
59,6006.75500 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
00Oct 10, 1994Jul 29, 1994Yes
00Aug 11, 1994——
00Jan 20, 1994Oct 5, 1993—
00Nov 3, 1993——
00Jan 29, 1990Nov 15, 1989Yes
00Jan 24, 1990——

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