TEXAS · WELLS · FORT BEND COUNTY · API 42-157-33093 · DISTRICT 03

Gordon #845

Shut in

Fort Bend County · Blue Ridge field · Shut In  · Vertical

Gordon #845 (API 42-157-33093) is a well in Fort Bend County operated by Blue Ridge Operating LLC, completed December 14, 2014 and listed as shut in on the RRC schedule, shut in October 1, 2019.

The RRC has issued one drilling permit, issued April 18, 2014, permitted to 3,443 ft.

It was permitted by Maverick Prod. CO., Inc. and has since transferred to Blue Ridge Operating LLC on the wellbore schedule.

Completion filings report 10 formation tops, including Frio, Caprock, Catahoula, Dome Caprock - Disposal.

Its 2 leases have reported 557K barrels of oil and 13 mcf of gas since January 1993, last reporting volume in April 2026. The leases carry 61 wells, so these are lease totals, not this well alone.

Operator of record

Blue Ridge Operating LLC

Permitted by Maverick Prod. Co., Inc.; the EWA schedule now lists a different operator.

Based in
Willis, TX
P-5 status
Active (A)
P-5 last filed
Aug 6, 2025
Permits on file
2
Phone
(832) 584-3363

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleBlue Ridge Operating LLC
Production reportsBlue Ridge Operating LLCthrough Apr 2026
Latest permitMaverick Prod. Co., Inc.Apr 18, 2014

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

3,443
total depth, ft
1
permits on file
Apr 18, 2014
last permit issued
Dec 14, 2014
completed
557K
cumulative oil, bbl
13
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · May 1993 THROUGH Apr 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Dec 14, 2014
Shut in
Oct 1, 2019
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 2 leases this well is completed on; they carry 61 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Gordon O-3-25694Blue RidgeBlue Ridge Operating LLC45391K0Apr 2011 – Apr 2026
Blakely E O-3-21225Blue RidgeBlue Ridge Operating LLC16166K13Jan 1993 – Dec 2024

Oil, barrels lease total

Last 12 months 387 · prior 12 649(-40%)

0200400202420252026

Chain of custody

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

  1. 1Sequoia Oil CompanyMay 1993 → Apr 1994
  2. 2Sawtooth, Inc.Nov 2001 → Oct 2009
  3. 3Maverick Prod. Co., Inc.Apr 2010 → Oct 2016
  4. 4Viceroy Petroleum, LPNov 2016 → May 2022
  5. 5Blue Ridge Operating LLCJun 2022 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
781760-99DrillMaverick Prod. Co., Inc.Mar 10, 2014Apr 18, 2014Sep 14, 20144,000

Completions

CompletedLeaseFieldOperatorStatusDepth
Dec 14, 2014Gordon O-3-25694Blue RidgeBlue Ridge Operating LLCShut In · shut in Oct 1, 20193,443
Dec 14, 2014Blakely E O-3-21225Blue RidgeBlue Ridge Operating LLCNot on Schedule—

Formation tops

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

FormationMD ftSubsea
FrioFRIO - DISPOSAL2,500-2,430
Frio2,700-2,630
CaprockCAPROCK - DISPOSAL——
CatahoulaCATAHOULA - DISPOSAL——
Dome Caprock - Disposal——
FrioFRIO - DISPOSAL——
Miocene (undifferentiated)MIOCENE - DISPOSAL——
Oligocene - Disposal——
Pliocene - Disposal——
Tiger (Miocene) - Disposal——
VicksburgVICKSBURG - DISPOSAL——
WilcoxWILCOX-COCKFIELD - DISPOSAL——

Perforations

Perforated and open-hole intervals.

FromToType
2,7162,756Perforated
3,1443,156Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62542011321 S
5.53,4127.875528 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 15, 2018Sep 11, 2017—
00Jan 29, 2016Dec 22, 2015—
00Jan 28, 2016Nov 23, 2015—
00Mar 12, 2015Dec 4, 2014Yes

Well logs

1 log loaded from the RRC's log index, the latest received Oct 20, 2017. Density, Neutron, 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
COMBINATION: RESISTIVITY/NEUTRON/DENSITY POROSITYSpans FrioTIFF420 to 3,443Oct 20, 2017run Sep 22, 20142.31

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