WELL · 42-029-38243 · DISTRICT 1

Klemcke Fred #9

N

Bexar County · Somerset field  · Vertical

Klemcke Fred #9 (API 42-029-38243) is a permitted well in Bexar County filed by Seagull Operating CO. Inc.; no completion report is on file yet.

The RRC has issued one drilling permit, issued November 27, 2002, permitted to 1,525 ft.

Completion filings report one formation top, including Olmos.

Its 2 leases have reported 22.2K barrels of oil and 38 mcf of gas since January 1993, last reporting in July 2026. The leases carry 12 wells, so these are lease totals, not this well alone.

Operator of record

Seagull Operating Co. Inc.

Shreveport, LA · P-5 Y, filed Jul 7, 2023 · 326 permits on file · (318) 226-9170

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleSeagull Operating Co. Inc.
Production reportsKoko Skadi, LLCthrough Apr 2026
Latest permitSeagull Operating Co. Inc.Nov 27, 2002

The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.

1,525
total depth, ft
1
permits on file
Nov 27, 2002
last permit issued
—
completed
22.2K
cumulative oil, bbl
38
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2026

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 12 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Klemke, Fred O-1-6498SomersetKoko Skadi, LLC1022.2K38Jan 1993 – Jul 2026
Klemcke, Fred O-1-14437SomersetSeagull Operating Co., Inc.200Feb 2003 – Jul 2003

Oil, barrels lease total

Last 12 months 331 · prior 12 555(-40%)

050100202420252026

Chain of custody

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

  1. 1Black Jack Well Service, Inc.Jan 1993 → Nov 1993
  2. 2Lucros International CorporationDec 1993 → Mar 1994
  3. 3Rife Oil Properties, Inc.Jun 1994 → Aug 1994
  4. 4Ginco Operating Co.Sep 1994 → Jan 1996
  5. 5Great Plains Resources, Inc.Jul 1996 → Dec 1997
  6. 6Seagull Operating Co., Inc.Feb 2001 → Aug 2022
  7. 7Koko Skadi, LLCOct 2022 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
525840-99DrillSeagull Operating Co. Inc.Nov 25, 2002Nov 27, 2002Jan 20, 20031,525

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-1-6498————
—— O-1-14437————

Formation tops

As filed on W-2/G-1. Download CSV →

FormationMD ft
Olmos1,414

Perforations

Perforated and open-hole intervals.

FromToType
1,4141,432Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
4.51,5066.75180 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
00Jul 14, 2003Jun 23, 2003Yes
00Jul 3, 2003——

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