WELL LOGS · UNITED STATES · ONE ROW PER LOG
Well logs within 2 mi of API 42-497-36660
Well logs loaded into Petrora from the regulators' log indexes, newest received first: what each measures, whether it is a digital LAS file or an image, the interval filed for it, and the formations it spans by the well's own tops. Loaded so far for Texas; more states and data sources will follow. Petrora lists these logs; each well's page links to the regulator for the files.
Distances are to the nearest location on file for each well (a horizontal has several along its path), in miles. Locations are surface and path points as mapped, not bottom-hole surveys.
15 LOG FILES ON 14 WELLS · A LOG'S LAS AND IMAGE IN ONE ROW · PAGE 1 OF 1
| Well | Distancemi | Logas described | Intervalft, as filed | Datereceived |
|---|---|---|---|---|
| Norton E. E. Unit #2HHZ42-497-36128Wise, TX · Eagleridge Operating LLC | 0.76 | Surveys Cased HoleTIFFGAMMA RAY RATE OF PENETRATION TEMPERATURE | 6,981 to 7,122 | Oct 19, 2007run Jan 25, 2007 |
| Norton E. E. Unit #2HHZ42-497-36128Wise, TX · Eagleridge Operating LLC | 0.76 | Surveys Cased HoleTIFFGAMMA RAY RATE OF PENETRATION TMPERATURE | 7,085 to 10,030 | Oct 18, 2007run Jan 16, 2007 |
| Hicks Lide #342-497-36024Wise, TX · BKV Barnett LLC | 0.95 | RESISTIVITYTIFF | 509 to 6,618 | Nov 6, 2009run Oct 25, 2006 |
| Busey-Gast Unit #8HHZ42-497-37688Wise, TX · Eagleridge Operating LLC | 1.16 | RESISTIVITYTIFF | 5,000 to 10,036 | Sep 9, 2016run Jul 17, 2013 |
| Mize #1HHZ42-497-37181Wise, TX · Eagleridge Operating LLC | 1.18 | RESISTIVITYTIFF | 6,255 to 11,466 | May 15, 2014run Jan 31, 2011 |
| Burns Arizona #442-497-33299Wise, TX · Devon Energy Production Co L.P. | 1.27 | RESISTIVITYTIFF | 484 to 7,551 | Dec 23, 2009run Jul 26, 1988 |
| Busey-Gast Unit #7HHZ42-497-37376Wise, TX · Eagleridge Operating LLC | 1.30 | RESISTIVITYTIFF | 5,000 to 11,104 | Aug 23, 2016run Jun 26, 2013 |
| Haynes Floyd GU #3HZ42-497-36925Wise, TX · BKV Barnett LLC | 1.33 | RESISTIVITYTIFF | 500 to 6,530 | May 8, 2013run Apr 13, 2010 |
| Busey-Gast Unit #1HHZ42-497-37098Wise, TX · Eagleridge Operating LLC | 1.37 | RESISTIVITYTIFF | 200 to 7,609 | Aug 21, 2013run Jul 19, 2010 |
| Simpson Ida #1HHZ42-497-37417Wise, TX · Eagleridge Operating LLC | 1.48 | Gamma RayTIFF | 451 to 3,320 | Feb 1, 2018 |
| Burns Arizona #542-497-35616Wise, TX · BKV Barnett LLC | 1.50 | ResistivityTIFFARRAY INDUCTION SHALLOW FOCUSED ELECTRIC LOG | 535 to 6,318 | Apr 15, 2008run Sep 1, 2004 |
| Whatley Unit #4HHZ42-497-37572Wise, TX · Eagleridge Operating LLC | 1.53 | RESISTIVITYTIFF | 3,828 to 7,102 | Feb 23, 2016run Feb 25, 2013 |
| Whatley Unit #1HHZ42-497-37409Wise, TX · Eagleridge Operating LLC | 1.86 | RESISTIVITYTIFF | 4,750 to 10,397 | Apr 15, 2015run Apr 10, 2012 |
| Reddell a Unit #1HHZ42-497-37423Wise, TX · Eagleridge Operating LLC | 1.96 | Gamma RayTIFF | 464 to 2,997 | Feb 1, 2018 |
| Stutt Robert #442-497-35599Wise, TX · BKV Barnett LLC | 1.99 | ResistivityTIFFARRAY INDUCTION SHALLOW FOCUSED ELECTRIC LOG | 497 to 6,388 | Apr 15, 2008run Aug 19, 2004 |
About this data
Well logs loaded into Petrora from the regulators' log indexes, so far for Texas, with more states and data sources to follow; not necessarily every log that exists. 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. A formation is spanned where the log's filed interval overlaps it in the well's own formation tops; both are measured depths as filed, so a horizontal's lateral is counted in the formation it ends in. Kinds are read from the regulator's description of each log, not from its curves. The date is when the log entered the RRC's imaged log database; a run date is shown where the index gives a different one (mostly logs before 2017: since digital filing began that year, the index gives the filing date for both). Nothing is estimated.
Developers: this page as JSON is GET /v1/data/logs, documented in the API reference.