TEXAS · WELLS · HOWARD COUNTY · KNIGHT "2" LEASE · API 42-227-36064 · DISTRICT 7B

Knight 2 #1

Shut in

Howard County · Spraberry (Trend Area) field · Shut In  · Vertical

Knight 2 #1 (API 42-227-36064) is a well in Howard County operated by Surge Operating LLC, completed September 1, 2007 and listed as shut in on the RRC schedule, shut in February 1, 2019.

The RRC has issued one drilling permit, issued June 4, 2007, permitted to 8,868 ft.

It was permitted by Crownquest Operating, LLC and has since transferred to Surge Operating LLC on the wellbore schedule.

Completion filings report 4 formation tops, including Rustler, Yates, San Andres, Spraberry.

Its lease has reported 17.2K barrels of oil and 30.3K mcf of gas since September 2007, with no volume in the three years through April 2026.

Operator of record

Surge Operating LLC

Permitted by Crownquest Operating, LLC; the EWA schedule now lists a different operator.

Based in
Houston, TX
P-5 status
Active – Extension (X)
P-5 last filed
Jul 14, 2026
Permits on file
1,234
Phone
(832) 333-2300

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleSurge Operating LLC
Production reportsSurge Operating, LLCthrough Apr 2018
Latest permitCrownquest Operating, LLCJun 4, 2007

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

8,868
total depth, ft
1
permits on file
Jun 4, 2007
last permit issued
Sep 1, 2007
completed
17.2K
cumulative oil, bbl
30.3K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · SEP 2007 THROUGH APR 2018

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Sep 1, 2007
Shut in
Feb 1, 2019
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.

Wells nearby

Every well with a location on file around this well, in any state, nearest first.

Loading the map…

Open the full map →

Texas locations come from drilling permits, so most older Texas wells have none and are not listed.

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
Knight "2" O-10-38445Spraberry (Trend Area)Surge Operating, LLC117.2K30.3KSep 2007 – Apr 2018

No volumes reported on these leases in the last three years.

Wells named Knight 2

Surge Operating LLC's other wells filed under this lease name in Howard County, newest permit first. The RRC gives a gas well its own lease number, so the name is what joins the wells of a unit.

Loading the lease's wells

Chain of custody

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

  1. 1Crownquest Operating, LLCSep 2007 → Nov 2010
  2. 2Linn Operating, Inc.Dec 2010 → Sep 2015
  3. 3JPM Eoc Operating, Inc.Oct 2015 → Sep 2016
  4. 4SM Energy CompanyOct 2016 → Jul 2017
  5. 5Surge Operating, LLCAug 2017 → Apr 2018

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
639717-99DrillCrownquest Operating, LLCMay 29, 2007Jun 4, 2007Jul 8, 20079,800

Completions

CompletedLeaseFieldOperatorStatusDepth
Sep 1, 2007Knight 2 O-10-38445Spraberry (Trend Area)Surge Operating LLCShut In · shut in Feb 1, 20198,868

Formation tops

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

FormationMD ftSubsea
Rustler1,4511,291
Yates2,007735
San Andres3,331-589
SpraberrySPRABERRY/DEAN7,720-4,978

Perforations

Perforated and open-hole intervals.

FromToType
7,7207,798Perforated
7,8748,018Perforated
8,1308,230Perforated
8,3508,617Perforated
8,7408,794Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
13.37531317.5400 S
8.6254,102111,200 S
5.58,8687.875725 S
5.5—7.875315 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
00Jan 24, 2008Oct 25, 2007Yes
00Jan 16, 2008——

Well logs

1 log loaded from the RRC's log index, the latest received Aug 3, 2010. Density, Neutron. 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
NEUTRON/DENSITY POROSITYSpans San Andres, SpraberryTIFF4,099 to 8,846Aug 3, 2010run Jul 23, 20078.15

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