WELL LOGS · UNITED STATES · ONE ROW PER LOG

Well logs within 2 mi of API 42-337-34883

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 API 42-337-34883Clear

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.

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

Well DistancemiLogas describedIntervalft, as filedDatereceived
Curry B Unit #1HHZ42-337-35137Montague, TX · BKV Barnett LLC0.64RESISTIVITYTIFF1,102 to 6,850Oct 31, 2018run Jul 15, 2013
McCall B Unit #1HZ42-337-35088Montague, TX · Eagleridge Operating LLC0.73COMBINATION: RESISTIVITY/NEUTRON/DENSITY POROSITYTIFF5,000 to 7,323Oct 28, 2016run Oct 13, 2013
McCall B Unit #1HZ42-337-35088Montague, TX · Eagleridge Operating LLC0.73RESISTIVITYTIFF1,322 to 7,323Oct 28, 2016run Oct 13, 2013
McCall B Unit #1HZ42-337-35088Montague, TX · Eagleridge Operating LLC0.73RESISTIVITYTIFF1,322 to 7,344Oct 28, 2016run Oct 13, 2013
McCall B Unit #1HZ42-337-35088Montague, TX · Eagleridge Operating LLC0.73RESISTIVITYTIFF1,322 to 7,360Oct 28, 2016run Oct 13, 2013
McCall B Unit #1HZ42-337-35088Montague, TX · Eagleridge Operating LLC0.73RESISTIVITYTIFF5,000 to 7,360Oct 28, 2016run Oct 13, 2013
McCall B Unit #1HZ42-337-35088Montague, TX · Eagleridge Operating LLC0.73RESISTIVITYTIFF5,000 to 7,788Oct 28, 2016run Oct 5, 2013
Collier a Unit #2HHZ42-337-34884Montague, TX · BKV Barnett LLC1.03RESISTIVITYTIFF1,104 to 7,710Jul 21, 2015run Jul 2, 2012
McCall a Unit #1HZ42-337-35087Montague, TX · Eagleridge Operating LLC1.05COMBINATION: RESISTIVITY/NEUTRON/DENSITY POROSITYTIFF1,342 to 7,290Jan 4, 2017run Oct 29, 2013
McCall a Unit #1HZ42-337-35087Montague, TX · Eagleridge Operating LLC1.05RESISTIVITYTIFF1,342 to 7,290Jan 4, 2017run Oct 29, 2013
McCall a Unit #1HZ42-337-35087Montague, TX · Eagleridge Operating LLC1.05RESISTIVITYTIFF1,342 to 7,307Jan 4, 2017run Oct 29, 2013
McCall a Unit #1HZ42-337-35087Montague, TX · Eagleridge Operating LLC1.05RESISTIVITYTIFF1,342 to 7,327Dec 30, 2016run Oct 29, 2013
McCall a Unit #1HZ42-337-35087Montague, TX · Eagleridge Operating LLC1.05RESISTIVITYTIFF1,342 to 7,327Jan 4, 2017run Oct 29, 2013
Fennel a Unit #2HHZ42-337-35048Montague, TX · BKV Barnett LLC1.14RESISTIVITYTIFF1,140 to 7,394Mar 9, 2016run Feb 18, 2013
Collier #1A42-337-34126Montague, TX · Watson Energy Investments LLC1.54RESISTIVITYTIFF1,097 to 7,670Feb 24, 2010run Nov 9, 2008
Nunnely E Unit #1HHZ42-337-35197Montague, TX · BKV Barnett LLC1.57RESISTIVITYTIFF1,129 to 7,102Oct 7, 2016run Oct 1, 2013
Sadie Unit #1HHZ42-337-34861Montague, TX · BKV Barnett LLC1.70RESISTIVITYTIFF1,152 to 7,371Jul 21, 2015run Jun 27, 2012
Sadie Unit #1HHZ42-337-34861Montague, TX · BKV Barnett LLC1.70RESISTIVITYTIFF1,152 to 7,371Mar 19, 2018run Jun 27, 2012
Nunnely D Unit #1HHZ42-337-35125Montague, TX · BKV Barnett LLC1.88RESISTIVITYTIFF0 to 6,900Jul 14, 2016run Jul 1, 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.