TEXAS · WELLS · HOWARD COUNTY · API 42-227-36444 · DISTRICT 7B

Hyman Sarah #57

Y

Howard County · Howard Glasscock (Consolidated) field · Producing  · Vertical

Hyman Sarah #57 (API 42-227-36444) is a well in Howard County operated by Citation Oil & Gas Corp., completed April 2, 2012 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued July 29, 2010, permitted to 4,246 ft.

It was permitted by Conocophillips Company and has since transferred to Citation Oil & Gas Corp. on the wellbore schedule.

Completion filings report 9 formation tops, including Yates, Svnr, Queen, Grayburg.

Its 2 leases have reported 966K barrels of oil and 234K mcf of gas since May 2011, last reporting volume in April 2026. The leases carry 41 wells, so these are lease totals, not this well alone.

Operator of record

Citation Oil & Gas Corp.

Permitted by Conocophillips Company; the EWA schedule now lists a different operator.

Based in
Houston, TX
P-5 status
Active – Extension (X)
P-5 last filed
May 27, 2026
Permits on file
866
Phone
(281) 891-1000

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleCitation Oil & Gas Corp.
Production reportsCitation Oil & Gas Corp.through Apr 2026
Latest permitConocophillips CompanyJul 29, 2010

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

4,246
total depth, ft
1
permits on file
Jul 29, 2010
last permit issued
Apr 2, 2012
completed
966K
cumulative oil, bbl
234K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · May 2011 THROUGH Apr 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Apr 2, 2012
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 2 leases this well is completed on; they carry 41 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Hyman, Sarah O-10-41242Howard Glasscock (Consolidated)Citation Oil & Gas Corp.40949K234KDec 2011 – Apr 2026
Hyman, Sarah O-10-41413Howard Glasscock (Clear Fork,mi)Conocophillips Company117.6K147May 2011 – Nov 2011

Oil, barrels lease total

Last 12 months 18,393 · prior 12 25,217(-27%)

01K2K3K202420252026

Gas, mcf lease total

Last 12 months 7,993 · prior 12 17,534(-54%)

01K2K3K202420252026

Chain of custody

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

  1. 1Conocophillips CompanyMay 2011 → Jan 2018
  2. 2Citation Oil & Gas Corp.Feb 2018 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
699763-99DrillConocophillips CompanyJul 28, 2010Jul 29, 2010Feb 13, 20114,400

Completions

CompletedLeaseFieldOperatorStatusDepth
Apr 2, 2012Hyman Sarah O-10-41242Howard Glasscock (Consolidated)Citation Oil & Gas Corp.Producing4,246
May 24, 2011Hyman Sarah O-10-41413Howard Glasscock (Clear Fork MI)Conocophillips CompanyNot on Schedule—

Formation tops

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

FormationMD ftSubsea
Yates1,2141,251
Svnr1,3001,165
Queen1,482983
Grayburg1,783682
San Andres2,099366
Glorieta2,620-155
Clear ForkCLEARFORK3,010-545
Tubb3,599-1,134
Wichita-AlbanyWICHITA ALBANY4,170-1,705

Perforations

Perforated and open-hole intervals.

FromToType
1,3311,443Perforated
1,5171,668Perforated
2,0342,081Perforated
2,1002,230Perforated
2,3732,596Perforated
2,6632,988Perforated
3,0343,543Perforated
3,0343,573Perforated
3,6104,140Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.6251,14912.25700 S
5.54,2317.875800 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. The record date is the RRC's own date on the record, not the day the report was filed: 462,034 of the state's filings carry 1984-01-12. About these reports →

SuffixRRC record dateW-2 / G-1 dateLogs referenced
00May 8, 2013Apr 13, 2012—
00May 19, 2012Jun 8, 2011Yes
00May 2, 2012Jun 8, 2011Yes

Well logs

1 log loaded from the RRC's log index, the latest received Jul 9, 2012. Resistivity. These are the logs loaded into Petrora from the Railroad Commission's inventories, not necessarily every log run on the well. The RRC holds the files; each opens from its log search for the well. The kind is the RRC's description of the log; the interval is the one filed for it.

Open the RRC's log search for this well ↗
Logas describedFiles Intervalft, as filedDatereceivedSizeMB
RESISTIVITYSpans Yates, Svnr, Queen, Grayburg, San Andres, Glorieta, Clear Fork, Tubb, Wichita-AlbanyTIFF1,150 to 4,248Jul 9, 2012run Feb 16, 20115.66

"Spans" is by this well's own filed formation tops: a formation runs from its top to the next deeper top filed, and the deepest runs to the bottom of the log. Depths are measured along the wellbore, so on a horizontal the lateral counts in the formation it was landed in.

Find logs withinmiles of this well:List →Map →

Search the well logs loaded into Petrora →

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.

The logs loaded for this well are under Well logs, with the RRC's log search for it.

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