WELL LOGS · UNITED STATES · ONE ROW PER LOG

Well logs within 2 mi of Talledega Unit #1H (42-337-35331)

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.

Within0.5 mi1 mi2 mi3 mi5 mi10 mi25 miof Talledega Unit #1H (42-337-35331)Clear

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.

17 LOG FILES ON 16 WELLS · A LOG'S LAS AND IMAGE IN ONE ROW · PAGE 1 OF 1

Well DistancemiLogas describedIntervalft, as filedDatereceived
Walthall Unit #2HHZ42-337-35199Montague, TX · BKV Barnett LLC0.54RESISTIVITYTIFF970 to 6,396Dec 21, 2016run Dec 15, 2013
Arnold a Unit #1HHZ42-337-35152Montague, TX · BKV Barnett LLC0.72COMBINATION: RESISTIVITY/NEUTRON/DENSITY POROSITYTIFF50 to 6,550Oct 5, 2016run Aug 26, 2013
Putnam C Unit #1HHZ42-337-35163Montague, TX · BKV Barnett LLC0.98RESISTIVITYTIFF912 to 6,628Dec 5, 2016run Sep 9, 2013
Arnold B Unit #1HHZ42-337-35154Montague, TX · BKV Barnett LLC1.00RESISTIVITYTIFF916 to 6,407Sep 9, 2016run Sep 4, 2013
Talledega Unit #1HHZ42-337-35331Montague, TX · BKV Barnett LLC1.11RESISTIVITYTIFF0 to 6,470May 12, 2017run May 13, 2014
Darlington a Unit #2HHZ42-337-35304Montague, TX · BKV Barnett LLC1.16RESISTIVITYTIFF0 to 6,450May 1, 2017run Apr 13, 2014
Putnam D Unit #1HHZ42-337-35165Montague, TX · BKV Barnett LLC1.26RESISTIVITYTIFF918 to 6,350Oct 31, 2018run Sep 22, 2013
Carmony C Unit #2HHZ42-337-35121Montague, TX · BKV Barnett LLC1.36RESISTIVITYTIFF0 to 6,480Jun 16, 2016run Jun 17, 2013
Marshall Unit #1HHZ42-337-35368Montague, TX · BKV Barnett LLC1.42COMBINATION: RESISTIVITY/NEUTRON/DENSITY POROSITYTIFF22 to 6,919Oct 31, 2018run Oct 12, 2014
Carmony B Unit #1HHZ42-337-35057Montague, TX · BKV Barnett LLC1.66RESISTIVITYTIFF200 to 6,450Mar 29, 2016run Mar 26, 2013
Rita Unit #1HHZ42-337-35175Montague, TX · BKV Barnett LLC1.72COMBINATION: RESISTIVITY/NEUTRON/DENSITY POROSITYTIFF50 to 6,443Sep 9, 2016run Sep 17, 2013
Friederich a Unit #2HHZ42-337-35358Montague, TX · BKV Barnett LLC1.77RESISTIVITYTIFF977 to 6,400Jun 12, 2017run Jun 26, 2014
Carmony B Unit #2HHZ42-337-35058Montague, TX · BKV Barnett LLC1.82RESISTIVITYTIFF956 to 6,510Mar 29, 2016run Mar 21, 2013
Pope B Unit #1HHZ42-337-35296Montague, TX · BKV Barnett LLC1.89RESISTIVITYTIFF50 to 6,348Mar 4, 2015run Feb 15, 2014
Pope B Unit #1HHZ42-337-35296Montague, TX · BKV Barnett LLC1.89RESISTIVITYTIFF50 to 6,348Feb 24, 2017run Feb 15, 2014
Putnam a Unit #1HHZ42-337-35031Montague, TX · BKV Barnett LLC1.90RESISTIVITYTIFF0 to 7,006Feb 8, 2016run Jan 14, 2013
Carmony a Unit #1HHZ42-337-35056Montague, TX · BKV Barnett LLC1.96RESISTIVITYTIFF0 to 6,500Mar 29, 2016run Mar 14, 2013

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.