WELL · 42-255-34356 · DISTRICT 2

Forshage-Howell Unit AC #1H

Shut in

Karnes County · Sugarkane (Austin Chalk) field · Temp Abandoned  · Horizontal

Forshage-Howell Unit AC #1H (API 42-255-34356) is a horizontal well in Karnes County operated by Marathon Oil EF LLC, completed July 28, 2015 and listed as temp abandoned on the RRC schedule, shut in January 1, 2026.

The RRC has issued one drilling permit, issued November 20, 2014, permitted to 12,325 ft.

Completion filings report 10 formation tops, including Yegua, Queen City, Reklaw, Carrizo.

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

Operator of record

Marathon Oil EF LLC

Based in
Houston, TX
P-5 status
Active (A)
P-5 last filed
Sep 26, 2025
Permits on file
3,191
Phone
(832) 486-2737

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleMarathon Oil EF LLC
Production reportsMarathon Oil EF LLCthrough Dec 2025
Latest permitMarathon Oil EF LLCNov 20, 2014
12,325
total depth, ft
1
permits on file
Nov 20, 2014
last permit issued
Jul 28, 2015
completed
0
cumulative oil, bbl
570K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jul 2015 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Jul 28, 2015
Shut in
Jan 1, 2026
Plugged
—

Operator's P-5 on the schedule: Active – Extension (X)

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
Forshage-Howell Unit AC G-2-279714Sugarkane (Austin Chalk)Marathon Oil EF LLC10570KJul 2015 – Jul 2026

Gas, mcf lease total

Last 12 months 7,739 · prior 12 11,334(-32%)

01K2K3K202420252026

Chain of custody

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

  1. 1Marathon Oil EF LLCJul 2015 → Dec 2025

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
800517-99DrillMarathon Oil EF LLCNov 19, 2014Nov 20, 2014Mar 10, 201517,500

Completions

CompletedLeaseFieldOperatorStatusDepth
Jul 28, 2015Forshage-Howell Unit AC G-2-279714Sugarkane (Austin Chalk)Marathon Oil EF LLCTemp Abandoned · shut in Jan 1, 202612,325

Formation tops

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

FormationMD ftSubsea
YeguaYEGUA - DISPOSAL2,018-1,511
Queen City4,410-3,903
Reklaw4,771-4,264
Carrizo5,292-4,785
WilcoxWILCOX - DISPOSAL6,464-5,957
Austin ChalkAUSTIN CHALK - H2S12,425-11,918
Eagle FordEAGLE FORD - H2S——
EdwardsEDWARDS - H2S——
FrioFRIO - DISPOSAL——
SligoSLIGO - H2S——

Perforations

Perforated and open-hole intervals.

FromToType
12,69516,184Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.6256,14712.251,780 S
5.516,2858.51,700 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 20, 2016Aug 27, 2015Yes

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