WELL · 42-227-36511 · DISTRICT 8

Ingram #1

N

Howard County  · Vertical

Ingram #1 (API 42-227-36511) is a permitted well in Howard County filed by Midland Oil And Gas, Inc.; no completion report is on file yet.

The RRC has issued 2 drilling permits (amended once) between 2010 and 2012, permitted to 11,000 ft.

Completion filings report 4 formation tops, including Clear Fork, Wouldhave Pay, Spraberry, Dean.

Its lease has reported 167K barrels of oil and 748K mcf of gas since January 2011, last reporting in July 2026. The lease carries 4 wells, so these are lease totals, not this well alone.

Operator of record

Midland Oil and Gas, Inc.

Midland, TX · P-5 Y, filed Jun 4, 2026 · 229 permits on file · (432) 661-1580

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulenone
Production reportsSM Energy Companythrough Dec 2022
Latest permitMidland Oil and Gas, Inc.Mar 26, 2012
11,000
total depth, ft
3
permits on file
Mar 26, 2012
last permit issued
—
completed
167K
cumulative oil, bbl
748K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 2011 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 lease this well is completed on; they carry 4 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Ingram O-10-40726Spraberry (Trend Area)New Height Energy, LLC4167K748KJan 2011 – 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. 1Midland Oil and Gas, Inc.Jan 2011 → Jul 2015
  2. 2Qstar Operating LLCAug 2015 → Dec 2016
  3. 3SM Energy CompanyJan 2017 → Nov 2022

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
734996-99RecompletionMidland Oil and Gas, Inc.Feb 29, 2012Mar 26, 2012—11,000
703510-98DrillMidland Oil and Gas, Inc.Oct 25, 2010Oct 15, 2010Nov 12, 201011,000
703510-99DrillMidland Oil and Gas, Inc.Oct 8, 2010Oct 15, 2010Nov 12, 201010,300

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-10-40726————

Formation tops

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

FormationMD ftSubsea
Clear ForkCLEARFORK4,418-1,868
Wouldhave Pay5,644-3,094
Clear ForkBASE CLEARFORK6,026-3,476
SpraberryUPPER SPRABERRY6,176-3,626
SpraberryLOWER SPRABERRY6,832-4,282
Dean7,560-5,010

Perforations

Perforated and open-hole intervals.

FromToType
7,5148,000Perforated
8,1668,702Perforated
9,0729,510Perforated
9,6789,868Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
13.37524417.5270 S
8.6253,505111,145 S
5.510,0247.875585 S
5.5—7.875625 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
00Jun 30, 2011Jan 24, 2011Yes
00Jun 23, 2011——

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